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
When DataTables content get too big it takes too long for full results to process or appear on the screen. Overall tables SHOULD come from a RESTful-like source with limits and offsets.
Lets start with a typically overloaded t_accounts. accounts/by_host.json may take more than 3 minutes to return after loading 30,000+ records. This is probably because the query join is too much to handle..
When DataTables content get too big it takes too long for full results to process or appear on the screen. Overall tables SHOULD come from a RESTful-like source with limits and offsets.
Lets start with a typically overloaded t_accounts. accounts/by_host.json may take more than 3 minutes to return after loading 30,000+ records. This is probably because the query join is too much to handle..
https://github.com/KvasirSecurity/Kvasir/blob/master/controllers/accounts.py#L546
Two things may help: first is AJAX with limit/offset, the second is a better query.
The text was updated successfully, but these errors were encountered: