Thank you all for the advice.
I asked the same question little differently phrased on postgresql-admin list and got several good answers from there as well. As result I implemented following changes:
Added 5 more processes to fastcgi, now we have 10 instead of 5 (thanks Curtis)
Changed search builder as Kenneth advised, thanks
Updated database server to version 8.4 (yeah, I know it is a development version and should not used for production purposes)
Heavily tuned the postgresql. The performance tuning advice on RT wiki is rather outdated but on Postgresql manual at http://www.postgresql.org/docs/8.3/interactive/runtime-config-resource.html is one very helpful comment (by Steven Citron-Pousty) on the subject.
The first user comment from this morning, roughly translated: “The RT now runs nearly with speed of light! Thank you”.
The parameters for our 4 gig server are now:
effective_cache_size = 2048MB
The work_mem is the “default” 1MB but I got recommendation (from Scott Marlowe) to change that to 4-8MB which I will do on the next maintenance. I did not change the max_fsm or checkpoint_segments so there is more room for improvement.
Lähettäjä: Jesse Vincent [mailto:firstname.lastname@example.org]
Lähetetty: 17. syyskuuta 2008 19:17
Vastaanottaja: Sahlberg Mauri
Aihe: Re: [rt-users] Performance problems with 3.8.1On Sep 17, 2008, at 6:13 AM, Sahlberg Mauri wrote:
Just upgraded from 3.6 to 3.8.1 (via 3.8) and at the same time moved the database to it’s own server. We also removed all closed tickets from the database. The move and upgrade was done as our old installation got too slow. Unfortunately the new installation is also very slow despite the ticket removal and dedicated database server. Especially search building view and ticket view take time to open.
So, what is slow and how slow is it?
Also, what can you tell us about your hardware specs?
I’ve worked with users for whom “slow” was “1.2s to load RT’s homepage” and with users for whom “slow” was “10 minutes to load a ticket page. It used to be five and that was ok. but 10 is too long.”