You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently on very big datasets in results or with big request stats some use cases are very slow and could take up to 2-3 seconds 😱. Big stats are quite a common thing for requests with multi schema.
Use cases:
Switching from History or Saved tab to Query tab if there are some results
Switching to results from stats and vice versa
What could be done:
Keep rendered elements on screen (for example with display: none), so they won't be calculated again. Applicable to result tables, stats, ast, explain plan and Fullscreen component
Optimise data calculations and rendering
Migrating QueryEditor files to TS is essential for this issue: #619
@antonkovalenko I've double checked the situation, and it still needs some improvements.
Huge tables are re-rendering every time we return to the tab with results (or switch to Fullscreen). Let's evaluate this issue as is.
Raubzeug
changed the title
Optimise QueryEditor
Optimise query results
Oct 2, 2024
Currently on very big datasets in results or with big request stats some use cases are very slow and could take up to 2-3 seconds 😱. Big stats are quite a common thing for requests with multi schema.
Use cases:
What could be done:
display: none
), so they won't be calculated again. Applicable to result tables, stats, ast, explain plan andFullscreen
componentMigrating
QueryEditor
files to TS is essential for this issue: #619Inspired by: #595 (comment)
The text was updated successfully, but these errors were encountered: