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
Since we updated the controllers to return the first 1000 items for each call, the various lists can now be quite long for larger sites.
I have a high traffic site, that over a given month somehow has been visited by more than 1000 different screen resolutions, so the page for Screen resolutions is roughly 1000 rows long. The site also has more than 1000 unique pages and more than 1000 sources, so the Views page is roughly 2000 rows long.
I'm not sure what the best approach for fixing this is, so I just wanted to write it here. There doesn't seems to be any performance issues, but perhaps we should add some pagination with Angular?
The text was updated successfully, but these errors were encountered:
OK just seen this @abjerner I need to figure out a best approach on how to do pagination client side unless @bjarnef you have any thoughts or ideas on this?
Since we updated the controllers to return the first 1000 items for each call, the various lists can now be quite long for larger sites.
I have a high traffic site, that over a given month somehow has been visited by more than 1000 different screen resolutions, so the page for Screen resolutions is roughly 1000 rows long. The site also has more than 1000 unique pages and more than 1000 sources, so the Views page is roughly 2000 rows long.
I'm not sure what the best approach for fixing this is, so I just wanted to write it here. There doesn't seems to be any performance issues, but perhaps we should add some pagination with Angular?
The text was updated successfully, but these errors were encountered: