On a recent project, I needed to render a very large amount of data on the client. Unfortunately, when it comes to rendering lots of templates, Blaze is slow. After lots of time profiling, debugging, and reading half-finished blog posts, I came to the conclusion that blaze just isn’t suited to rendering a very large number of templates.
So instead of using Blaze directly, I decided to let Clusterize.js manage the heavy lifting of render management. I wrote a blog post describing the process of incorporating Clusterize into a Blaze-based application. It also touches on dealing with client-side caching and maintaining dynamic UI updates.
Hopefully this helps some people out there.
As a note for future work, @loren mentioned forking Clusterize and adding native support for Blaze nodes to preserve reactivity in a more sane way. This would be an awesome improvement, and anyone doing this kind of work in the future should consider looking into it!