Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Long delay to open save layout dialog #101

Open
cfisher-scottlogic opened this issue Nov 9, 2023 · 0 comments
Open

Long delay to open save layout dialog #101

cfisher-scottlogic opened this issue Nov 9, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@cfisher-scottlogic
Copy link

cfisher-scottlogic commented Nov 9, 2023

Background

The 'save layout dialog' takes a really long time to open in certain situations. It appears to be isolated to when there are multiple components on the page where lots of data is being continually updated.

Reproduction Steps

  1. Run the showcase from vuu-ui (npm build then npm run showcase:build)
  2. Open "ShellWithNewThemeAndLayoutManagement
  3. Customise a layout which has frequent data updates (specific configuration I used below)

Image

  1. Open the context menu on the main tab header
  2. Click "Save Layout"

Expected Behaviour

The Save Layout dialog shows within a couple of seconds, although ideally it would be almost instantaneous.

Actual Behaviour

The Save Layout dialog shows after ~10 seconds

Possible solutions

  • Identify what the problem is (slow screenshot generation?)
  • Make sure Dialog opening is not reliant on a screenshot being generated
    • if screenshot generation is slow, consider using a spinner as the screenshot placeholder whilst it's being generated
  • Suspend the updates (see dataSource.suspend?.(); in useFilterTable.tsx)

Notes

I don't remember consciously load-testing the functionality with a high quantity of high frequency data tables at any point, so I can't be certain when this was introduced. The culprit could be as far back as the screenshot implementation, or it could be a more recent 'persistence implementation' problem. Investigation required.

These warnings appear in the console, though I'm not sure if they're related to the issue:

Image

@cfisher-scottlogic cfisher-scottlogic added the bug Something isn't working label Nov 9, 2023
@cfisher-scottlogic cfisher-scottlogic added this to the Layout Management milestone Nov 9, 2023
@vferraro-scottlogic vferraro-scottlogic self-assigned this Nov 21, 2023
@vferraro-scottlogic vferraro-scottlogic linked a pull request Nov 28, 2023 that will close this issue
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants