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 sending queries for hashes, tasks, etc. the UI always sets the max to 3000. Depending on the hashes (e.g. archive hashes) this quickly can lead into memory limit exceeding on the server side when it loads the up to 3000 hashes at once.
The UI should not request so many hashes (or other entries) at once, but doing multiple queries (with ranges) after each other if it wants to process all hashes (e.g. for the dashboard page). A limit of something between 100 and 500 would make more sense. Otherwise, also the tasks page is not really loading any faster than the old interface where it just loads all tasks (as long as there are less than 3000 tasks).
EDIT: just a side note regarding when having the UI running with this. When staying on the dashboard page for a longer time with these errors in the background, it stops working completely at some point as it gets the 500 errors for the queries every time it updates. Also the limit on the server for the memory limit (which is reached) is set to 256MB.
The text was updated successfully, but these errors were encountered:
When sending queries for hashes, tasks, etc. the UI always sets the max to 3000. Depending on the hashes (e.g. archive hashes) this quickly can lead into memory limit exceeding on the server side when it loads the up to 3000 hashes at once.
The UI should not request so many hashes (or other entries) at once, but doing multiple queries (with ranges) after each other if it wants to process all hashes (e.g. for the dashboard page). A limit of something between 100 and 500 would make more sense. Otherwise, also the tasks page is not really loading any faster than the old interface where it just loads all tasks (as long as there are less than 3000 tasks).
EDIT: just a side note regarding when having the UI running with this. When staying on the dashboard page for a longer time with these errors in the background, it stops working completely at some point as it gets the 500 errors for the queries every time it updates. Also the limit on the server for the memory limit (which is reached) is set to 256MB.
The text was updated successfully, but these errors were encountered: