Look at the following timeline and look for to optimizations to the "loadDocument" section:

mercedes-disable-chartView-with-startup-TimelineRawData-20170830T175747.json

My hunch is it shouldn't take ~100ms per document rendered on screen.

If no optimizations can be found then some kind of justification of the genuine reason to consume O(10^8) CPU clock cycles.

Then additional workarounds like deferring the rendering could be explored, i.e. Compass renders just the first 1-2 documents, making the GUI responsive again by unblocking the JS event loop, and then in the background Compass renders the remaining 18 documents.