-
Notifications
You must be signed in to change notification settings - Fork 28
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
Reduce memory requirements #118
Comments
For me, this issue is even worse, that page consuming about 1.5 GB of memory (or that's what Chrome reports) after scrolling through it a little bit. How should this problem be handled?
|
I was talking about server side memory consumption, on the client side it's huge as well :-). |
My Safari ended hanging up on first time. I think we should split up incidents as @udan11 suggested so that such reports do not consume 200MB directly to generate this report and also there will be no need to scroll to bottom to view graphs |
I believe that the two issues (client-sided and server-sided) are related. |
Even with PHP memory limit set to 512MB, some issues fail to render, for example: https://reports.phpmyadmin.net/reports/view/26036 Error is:
|
Rendering report with about 5000 incidents currently consumes about 200 MB on the server to generate. This should be reduced.
Example of such report: https://reports.phpmyadmin.net/reports/view/18227
The text was updated successfully, but these errors were encountered: