Uploaded image for project: 'Compass '
  1. Compass
  2. COMPASS-1861

Spike: Investigate hadron-document optimizations

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • CRUD, Performance
    • None

    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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            peter.schmidt Peter Schmidt
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: