-
Notifications
You must be signed in to change notification settings - Fork 516
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
Max rows displayed option #459
Comments
@tim-lukacik Tim, a pull request would be appreciated. Just make sure it works will all the features (grouping, filtering, select all, none, reset, etc). |
Yes, im also facing a lot of performance issues with this control.. |
@Wingie Take a look at #460. I found a limit of 500 to work acceptably on my machine so I suggested that as default. Seems to work with everything. It's just limiting what's displayed, not actually touching any arrays. It could potentially cause a group to not be fully listed if the group happens to be around the limit. |
A better solution would be pagination here instead :) |
Or maybe a solution that involved "virtual rows" or something.. like i have the need to put multiple dynamically changing multiselects on a [Wilson Wingston Sharon] On Wed, Jul 20, 2016 at 7:01 PM, Tim Lukacik notifications@github.com
|
If you haven't already, check out ui-grid. |
Why not solve performance issues on large result sets by adding a max rows displayed attribute? I added this, put a limitTo filter on the repeat for the results display, and put a "Display first X rows" at the bottom with a ng-if checking if the filteredresults length is > the max rows.
The search function still works this way and now the enormous lag (I have ~5k records sometimes) is completely gone. The code is very minimal, but I can create a pull request if you'd like.
Thank you for this excellent control!
The text was updated successfully, but these errors were encountered: