Tracing View Page Load Performance

Jump to bottom Edit New page

Daniel edited this page May 30, 2018 · 3 revisions

This page shows some historic reference performance measurements of the tracing view page load performance. The interval that is measured starts with the tracing view page load and stops once all orthogonal views are fully filled with data.

Measurements were executed using this NML file with 700,000 nodes (4000 trees of 175 nodes) and the Chrome DevTools.

Measurement 1

Commit: 4de6743abf2be0512671197ecd27b7a657194daf
Date: 30 May 2018
By: Daniel
Configuration: 64-bit, i7-5600U CPU (2.60GHz), 8GB RAM, Intel HD Graphics 5500, Ubuntu 16.04 (kernel 4.13.0-44), Chrome 66
Local/Deployment: Dev-Deployment

Overall time: 16s

Initial page load: 2s
Tracing download: 2.4s
Tracing parsing: 2.2s
Javascript initialization code: 5.7s
Data fetching and rendering: 3.5s

Chrome Perfomance Tab Screenshot: