mitar / meteor-web-rendering-framework-benchmark Goto Github PK

Currently, we benchmark only what happens when whole structure changes (like what would happen when router changes a page), but now when structure stays the same and just data updates. We should benchmark that as well.

Results have higher instability than what I would like. Both during multiple iterations inside one run, but also across multiple runs. Not sure how this could be improved. Maybe by running the benchmark on a dedicated machine without any other interference at the same time?

To compare with stateless Vue components.

And potentially other optimizations, like pure components.

In our app we figured out, that blaze begins to slow down at around 75 entries that are rendered with the same template. After around 250 templates, it feels really laggy.

So the increase of numbers of data to render is not linear to the rendering time

I would be interested if this is also the case with other rendering engines like Vue and react.