[COMPASS-1861] Spike: Investigate hadron-document optimizations Created: 30/Aug/17  Updated: 27/Oct/23  Resolved: 01/Oct/18

Status: Closed
Project: Compass
Component/s: CRUD, Performance
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Peter Schmidt Assignee: Unassigned
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File hadron-document spends up to 100ms per document, much of it waiting for random bytes.png     File mercedes-disable-chartView-with-startup-TimelineRawData-20170830T175747.json    
Issue Links:
Related
Epic Link: COMPASS-1739

 Description   

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.



 Comments   
Comment by Durran Jordan [ 01/Oct/18 ]

Rewriting stories to remove hadron-document

Generated at Wed Feb 07 22:28:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.