I have done the tests in debug mode because profile mode is not supported on the web. I agree with you that a real serious test should be done with external tools in release mode, but for the subject of this article (which is to show the performance differences between Flutter 2 and Flutter 3) I believe that doing the test in debug mode is sufficient enough.
It really is not. Testing Flutter in debug mode is unfortunately a totally meaningless measure. As a Flutter developer I have to say it just does not say anything about production speed.
Might as well read the tea leaves.
So it would be good to repeat this test with release mode. Then it makes sense.
As a Flutter developer I have to say it just does not say anything about production speed.
If you look closely at the article you will see that I do not intend to demonstrate anything about the speed in production, in fact my experiment goes in another direction, which is to observe the differences between Flutter 2 and Flutter 3, that is, to measure relatively how much has improved.
Both tests have been executed under the same parameters, with which the result is the performance differential between the two.
The adjustment that you are commenting on makes sense if what is intended is to demonstrate production performance, but that is not the objective of my article.
Dev environment performance is irrelevant. Why would the Flutter team take time to improve dev performance at all? There's no need for it and no reason, therefore even if they had made production 20x faster, the dev environment may be the exact same as before. Any speed improvements that "happen" to dev are accidental. Therefore it doesn't make sense to measure it.
It's a bit like a speed race with no tires on. You can race some cars with no tires on , and some will work better than others without tires, but it's not really measuring anything that has meaning.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Testing performance in debug mode isn't accurate. Absolutely need to test in release mode.
I have done the tests in debug mode because profile mode is not supported on the web. I agree with you that a real serious test should be done with external tools in release mode, but for the subject of this article (which is to show the performance differences between Flutter 2 and Flutter 3) I believe that doing the test in debug mode is sufficient enough.
It really is not. Testing Flutter in debug mode is unfortunately a totally meaningless measure. As a Flutter developer I have to say it just does not say anything about production speed.
Might as well read the tea leaves.
So it would be good to repeat this test with release mode. Then it makes sense.
If you look closely at the article you will see that I do not intend to demonstrate anything about the speed in production, in fact my experiment goes in another direction, which is to observe the differences between Flutter 2 and Flutter 3, that is, to measure relatively how much has improved.
Both tests have been executed under the same parameters, with which the result is the performance differential between the two.
The adjustment that you are commenting on makes sense if what is intended is to demonstrate production performance, but that is not the objective of my article.
I am saying only production performance matters.
Dev environment performance is irrelevant. Why would the Flutter team take time to improve dev performance at all? There's no need for it and no reason, therefore even if they had made production 20x faster, the dev environment may be the exact same as before. Any speed improvements that "happen" to dev are accidental. Therefore it doesn't make sense to measure it.
It's a bit like a speed race with no tires on. You can race some cars with no tires on , and some will work better than others without tires, but it's not really measuring anything that has meaning.