harrycheung
Clarify number of iterations on benchmark graphs
It would be great if you clarify if the beautiful graphs here:
https://medium.com/@harrycheung/mobile-app-performance-redux-e512be94f976#.1v6ezq7su
are based on 1,000 or 10,000 iterations runs. Maybe I missed it somewhere, but it's not 100% obvious to me since the source code for the different implementations support both variants.
Ah, the description in the original article makes it a bit clearer I think. You're reporting the performance for 1,000 iterations and only using the 10,000 iterations version to look at memory performance, right?
Yup, you are correct. Sorry it wasn't clear. I'm not that prolific and writing is not my forte.
On Tue, Apr 19, 2016 at 1:03 PM, Kasper Lund [email protected] wrote:
Ah, the description in the original article makes it a bit clearer I think. You're reporting the performance for 1,000 iterations and only using the 10,000 iterations version to look at memory performance, right?
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/harrycheung/Mobile-App-Performance/issues/18#issuecomment-212103565
Is there another/newer report about the performance outputs? One, that would cover also JavaScript, Unity and the other projects in this repo?
