knaeckekami / changenotifier_benchmark Goto Github PK

Hi,

I know this is not exactly within the scope of benchmarking change notifier solutions but it is super interesting to see the tradeoffs with using streams as well. I believe the micro benchmark from getx was including some stream solutions and it was super interesting to see the results but the display of them was really poor and the broken english did not exactly help communicate those.

The 2 dimensions micro benchmark you put in place is much cleaner in that regard and the output table format is pretty clear.

Would love to see how stream implementations compare.

When looking at the benchmark, we focus essentially on performance on the scale of how fast we can notify listeners but on constrained devices like mobiles, especially when you are trying to target as many of them and not just the latest generation, memory footprint is essential.

I was wondering if there is any way to measure and compare this between solutions ? I did not look into the implementations but it's common that one way to speed up things is to memoize / index and it usually come at the expense of memory so while one solution might be faster than another it might put too much pressure on the memory.

Just trying to open the conversation and see what is the general consensus on this subject. I believe I read that the author of getx was particularly surprised to notice how much memory the default stream implementation is consuming for example and that was what probably motivated him to develop some alternate stream solutions.