Redmine

Another interesting thing is that it takes a long time rendering a page, for example displaying new issue from production.log:

Rendered issues/new.html.erb within layouts/base (6283.2ms)
Completed 200 OK in 8556.7ms (Views: 6198.0ms | ActiveRecord: 401.8ms)

Hello Jorge,
Which web server are you using? Apache2/Passenger?
Did you run OPTIMIZE TABLE as advised?
Cheers,

Hi Martin,

Thank you for your reply. I'm using Apache2/Passenger. I ran Optimize Table on 4 tables (btw this tables are InnoDB) to test:

• users
• issues
• journals
• journal_details

On every case I got this:

mysql> optimize table users;
+---------------+----------+----------+-------------------------------------------------------------------+
| Table         | Op       | Msg_type | Msg_text                                                          |
+---------------+----------+----------+-------------------------------------------------------------------+
| redmine.users | optimize | note     | Table does not support optimize, doing recreate + analyze instead |
| redmine.users | optimize | status   | OK                                                                |
+---------------+----------+----------+-------------------------------------------------------------------+
2 rows in set (18.40 sec)

mysql> optimize table issues;
+----------------+----------+----------+-------------------------------------------------------------------+
| Table          | Op       | Msg_type | Msg_text                                                          |
+----------------+----------+----------+-------------------------------------------------------------------+
| redmine.issues | optimize | note     | Table does not support optimize, doing recreate + analyze instead |
| redmine.issues | optimize | status   | OK                                                                |
+----------------+----------+----------+-------------------------------------------------------------------+
2 rows in set (16.37 sec)

mysql> optimize table journals;
+------------------+----------+----------+-------------------------------------------------------------------+
| Table            | Op       | Msg_type | Msg_text                                                          |
+------------------+----------+----------+-------------------------------------------------------------------+
| redmine.journals | optimize | note     | Table does not support optimize, doing recreate + analyze instead |
| redmine.journals | optimize | status   | OK                                                                |
+------------------+----------+----------+-------------------------------------------------------------------+
2 rows in set (16.64 sec)

mysql> optimize table journal_details;
+-------------------------+----------+----------+-------------------------------------------------------------------+
| Table                   | Op       | Msg_type | Msg_text                                                          |
+-------------------------+----------+----------+-------------------------------------------------------------------+
| redmine.journal_details | optimize | note     | Table does not support optimize, doing recreate + analyze instead |
| redmine.journal_details | optimize | status   | OK                                                                |
+-------------------------+----------+----------+-------------------------------------------------------------------+
2 rows in set (3.37 sec)

What your passenger-status --verbose looks like during work hours?
And your Passenger configuration file?

Hi and thanks for the reply.

passenger-status --verbose looks like this:

# passenger-status --verbose
Version : 4.0.37
Date    : 2014-08-28 16:26:43 +0200
Instance: 1762
----------- General information -----------
Max pool size : 6
Processes     : 2
Requests in top-level queue : 0

----------- Application groups -----------
/usr/local/lib/redmine#default:
  App root: /usr/local/lib/redmine
  Requests in queue: 0
  * PID: 14720   Sessions: 1       Processed: 118     Uptime: 21m 21s
    CPU: 4%      Memory  : 346M    Last used: 2s ago
    URL     : http://127.0.0.1:59957
    Password: IUstn4GTNS2vwFgLqgnz86KOYtgfAlRLL5Dl3xfAnDZ
  * PID: 17759   Sessions: 0       Processed: 0       Uptime: 10s
    CPU: 0%      Memory  : 9M      Last used: 10s ago
    URL     : http://127.0.0.1:40013
    Password: c0NP9MtrnOlcxlUzA23x6Ae0jBXG8VLG1YosebqnYin

My Passenger configuration file just looks like this:

# cat /etc/apache2/mods-enabled/passenger.conf
PassengerRoot /usr/local/lib/passenger
PassengerRuby /usr/bin/ruby
PassengerDefaultUser www-data

Thanks for the help.

• PassengerMinInstances
• PassengerMaxPoolSize
• PassengerPoolIdleTime
• RailsAppSpawnerIdleTime

Be careful also that more is not always better. If for example you allow more instances than you server can handle, you could slow down the performances.
To mention it, it seems Puma (rewrite of Mongrel) is the fastest Rails server around to handle big loads. I didn't have the occasion to test it with Redmine yet.
Cheers,

Great, I will go down that road then. Try tuning passenger and testing Puma.

Thanks a lot for your time.

I hope it helps. I'll be interested to hear about your findings.
I suggest you to establish a baseline before tweaking the configuation to be able to measure your improvements.
Looking forwarding hear from you :)

Hi Martin,

Everything is working better now with version 2.4.2. I tried different roads but at the end using new ruby version is what did it best. This is what I tried:

• Using Puma: No change here, we got the same delivery times on each page.
• Adding caches to Apache and Varnish: This was a desperate attempt because it has nothing to do with database queries or rendering. No effect at all.
• Tuning passenger's configuration options: Read the docs and tried everything, small to none effect.
• Switch from Ruby 1.9.3 (Debian package) to Ruby 2.1.2 (Manual install): Win! Win! Win!

We got to a point that pages like "new issue" with thousands of users in project where taking as much as 25 seconds in being displayed. Now we got it down to 6 seconds.

So we're back to loving Redmine again. Hope things remain stable for a while.

Regards

Very interesting, thanks for the feedback :)

Hi Jorge,
How can you Switch from Ruby 1.9.3 (Debian package) to Ruby 2.1.2? Now my redmine version is 2.5.0,but the ruby version is 1.9.3,I want to just upgrade the ruby form 1.9.3 to 2.1.3. I install ruby 2.1.3 in my localhost,but it doesnot work, the redmine's ruby version is still 1.9.3。
Look forward to your reply.

apt-get purge ruby-1.9.3
and then try to use RVM.

Thank you very much for your reply:
My redmine is installed in windows 2012 by one click installation, but in the control panel, I cannot find the ruby 1.9.3. So how can I switch from ruby 1.9.3 to ruby 2.1.3 in windows?