Defect #40728
open
Global Spent Time Loading Issue after Redmine Enhancement
Added by Kaustubh Patil 6 months ago.
Updated 6 months ago.
Description
While loading the global spent time the website is taking too long to respond, usually taking more than 3 minutes. sometimes it doesn’t even load the data.
Environment:
Redmine version 5.1.2.stable
Ruby version 3.2.4-p170 (2024-04-23) [x86_64-linux]
Rails version 6.1.7.7
Environment production
Database adapter Mysql2
Mailer queue ActiveJob::QueueAdapters::SidekiqAdapter
Mailer delivery smtp
Redmine settings:
Redmine theme Zenmine-510 (includes JavaScript)
SCM:
Subversion 1.14.2
Mercurial 6.3.2
Bazaar 3.3.2
Git 2.39.2
Filesystem
Redmine plugins:
redmine_agile 1.6.9
redmine_budgets 1.0.5
redmine_checklists 3.1.23
redmine_contacts 4.4.1
redmine_contacts_helpdesk 4.2.2
redmine_contacts_invoices 4.2.9
redmine_reporter 2.0.4
- Status changed from New to Needs feedback
There is a limit on the number of time entries displayed per page. The available values can be set by admins and should be set to reasonable values. Redmine is not intended to show thousands of entries per page and slowdowns or timeouts are expected in this case. A reasonable max number of 100 entries per page. Thus, make sure you have configured reasonable per page limits in Administration -> Settings -> General -> Objects per page options.
If these values are reasonable in your case, we need more information about your Redmine and the amount of data which may allow us to reproduce this.
Hello Holger, we are aware about the same and i.e why we have kept objects per page and search results per page to a limit of 25. I would also like to highlight that the mentioned issue is only observed in the root user. For non-admin users the global spent time loads seamlessly.
In that case, please provide additional information which allows us to reproduce this issue:
- How many time entries are there overall?
- Are you using filters? Are you using a lot of custom fields?
- Check your Redmine logs in
logs/production.log on your server. I possible, try to raise the log level before trying by editing config/additional_environment.rb. There is an example file named config/additional_environment.rb.example. Check for any long-running SQL statements.
You are using a lot of plugins which may change behavior in this area of code. Try if you can reproduce this issue after you have disabled all plugins. You can also contact the plugin authors if they change anything in the area of time entries.
Also available in: Atom
PDF
Updated by 
Updated by