[
https://issues.apache.org/jira/browse/IGNITE-27580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Chesnokov updated IGNITE-27580:
-----------------------------------------
Description:
h2. Problem
The PerfStat HTML report stores all system views data in a single data.json.js
file. For large clusters this file can be hundreds of MB, which causes long
load times and Chrome freezes due to parsing and rendering huge arrays.
h2. Proposed solution
Split system views data into small chunked JSON files and add a meta.json per
view (columns, row counts per node, chunk size). Update systemViewTab.js to
load rows lazily and build the total view using metadata without loading all
rows at once. This should keep the report responsive for large datasets
h3. Limitations
Proposed solution has two disadvantages:
* It removes an option to sort views in html tables
* It removes an option to search through system view rows
For that tasks user can use grep over json
was:
The PerfStat HTML report stores all system views data in a single data.json.js
file. For large clusters this file can be hundreds of MB, which causes long
load times and Chrome freezes due to parsing and rendering huge arrays.
Split system views data into small chunked JSON files and add a meta.json per
view (columns, row counts per node, chunk size). Update systemViewTab.js to
load rows lazily (server-side pagination) and build the total view using
metadata without loading all rows at once. This should keep the report
responsive for large datasets
> [perfStat] Reduce memory usage in system views report generation
> ----------------------------------------------------------------
>
> Key: IGNITE-27580
> URL: https://issues.apache.org/jira/browse/IGNITE-27580
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Aleksandr Chesnokov
> Assignee: Aleksandr Chesnokov
> Priority: Major
> Labels: IEP-35, ise
>
> h2. Problem
> The PerfStat HTML report stores all system views data in a single
> data.json.js file. For large clusters this file can be hundreds of MB, which
> causes long load times and Chrome freezes due to parsing and rendering huge
> arrays.
> h2. Proposed solution
> Split system views data into small chunked JSON files and add a meta.json per
> view (columns, row counts per node, chunk size). Update systemViewTab.js to
> load rows lazily and build the total view using metadata without loading all
> rows at once. This should keep the report responsive for large datasets
> h3. Limitations
> Proposed solution has two disadvantages:
> * It removes an option to sort views in html tables
> * It removes an option to search through system view rows
> For that tasks user can use grep over json
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
