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

Pages with 500+ selectable items in a single able can suffer from poor performance #2565

Closed
cigamit opened this issue Mar 24, 2019 · 1 comment
Labels
bug Undesired behaviour resolved A fixed issue
Milestone

Comments

@cigamit
Copy link
Member

cigamit commented Mar 24, 2019

Describe the bug
The table rows and checkbox selectors have poor performance for very large tables due to the use of anonymous functions which delay the rendering on very large tables.

To Reproduce
Steps to reproduce the behavior:

  1. Goto a page that has several thousand rows, like Data Sources or Graphs
  2. Press the Go Button
  3. Modify the URL and change rows=XXX to rows=10000 and press enter to load the URL
  4. Notice the load time and JavaScript warnings on the page related to a hung script

Expected behavior
Though expected to be slower due to the number of rows, it should not hang the page.

Additional context
Eventually, with continued refinement of the JavaScript behavior, we should be able to increase the maximum rows on a page beyond 500.

cigamit added a commit that referenced this issue Mar 24, 2019
Table checkbox and row selection performance poor on large pages
@cigamit cigamit added bug Undesired behaviour resolved A fixed issue labels Mar 24, 2019
@cigamit
Copy link
Member Author

cigamit commented Mar 24, 2019

Happily resolved.

@cigamit cigamit closed this as completed Mar 24, 2019
@netniV netniV added this to the v1.2.3 milestone Mar 28, 2019
@netniV netniV changed the title Table checkbox and row selection performance poor on large pages Pages with 500+ selectable items in a single able can suffer from poor performance Mar 30, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Undesired behaviour resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

2 participants