I am trying to execute a reports which has 50 rows per page and 84 pages (approximated 4200 rows). I tried to click on a column to sort it and got this error.
'maximum execution time of 30 seconds exceeded'
I had two questions:
1) Are all the 84 pages prefetched? Looked like that because my browser was consuming a lot of memory. In FF (3.6) it hanged for a while. Chrome was OK.
2) Are these parameters configurable? Max execution time?
Regards,
Mitul
myDBR Team, Key Master
1) Are all the 84 pages prefetched? Looked like that because my browser was consuming a lot of memory. In FF (3.6) it hanged for a while. Chrome was OK.
Having a report of 84 pages will take some time to parse depending on the browser. The table sorting is done in client using javascript so the timeout also depends on the browser. if the performance is an issue, you might want to consider breaking up the report to smaller pieces and use the linked report to have drill down to details.
2) Are these parameters configurable? Max execution time?
The error message would indicate that you are reaching the limit set in php.ini. Look for the max_execution_time value defined in the php.ini.
--
myDBR Team
rnavarro, Member
myDBR Team, I am not sure if the question posted by Key Master asking if all 84 pages were prefetched was answered. Anyway I am experiencing the same problem.
I ran a query over a large table from MySQL Workbench and even tho it takes several minutes to run, it completed successfully over there.
I brought the same query to myDBR and it timed out.
I would like to know what are the options in myDBR to create pages when listing a large report, do them include a navigation bar or similar?
Any other way to resolve the timeout issue different to increase the time out on MySQL (right now it is 500 seconds and I never see a timeout when using Workbench even with more complex and longer reports).
To make it clear, there not joins or complex query elements or charts.
Regards,
RN
myDBR Team, Key Master
Any other way to resolve the timeout issue different to increase the time out on MySQL (right now it is 500 seconds and I never see a timeout when using Workbench even with more complex and longer reports).
The timeout you are getting is most likely the PHP script timing out. When your slow report query is sent to the database, PHP times out while waiting for the result from the database. This is a configuration of your PHP installation, not the database.
You can change the PHP timeout by changing the php.ini (max_execution_time) or by .htaccess file (php_value max_execution_time). Which method to choose depends on your installation and used web server.
If your report produces a lot of data and you really need all that data inside one report, you are better off if you choose a fast browser.
--
myDBR Team
You must log in to post.
