Slow ticket creation with postgres?

Hi,

Details.
postgres 7.2.3
RT. 2.0.11

In an attempt to speed things up a bit on our RT2 system, I’m playing with
converting the database from
mysql to postgres. I’m finding postgres to be somewhat slower in general,
but expect it to hold up
better in a multi user environment that mysql. However, when I go to create
a new ticket
via the WebUI, it takes about 40 seconds to bring up the ticket creation
window, this doesn’t take anywhere
near that long in mysql?

I’ve put postgres into debug_level 2, and it seems that it is doing ALOT of
queries to workout who has the rights to own tickets in
the queue i’m creating the ticket in. I’m using the standard indexes that
ship with rt2.0.11

Any hints as to how to speed this up?
Matthew Watson
Development, Netspace Online Systems
mwatson@netspace.net.au
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.394 / Virus Database: 224 - Release Date: 3/10/2002

“MW” == Matthew Watson mwatson@netspace.net.au writes:

MW> Any hints as to how to speed this up?

How big is your DB? How much SHM did you allow Postgres to use? Did
you “vacuum analyze” your tables recently (or frequently)?

It is plenty fast for us.

I just need to get around to purging the dead tickets… laziness
keeps me from doing it.

the database is about 400,000 tickets (which works out to be a little under
4 million rows across all tables)

Yep vacuum analyzed it, (its a new import, shouldn’t be alot for it to do.)

my memory setups are as follows

shared_buffers = 30400
max_fsm_relations = 500
max_fsm_pages = 10000
sort_mem = 32168
fsync = false

for most pages is it comparable to mysql, however for the create new ticket
page, its about 10 times slower. I’ve checked the indexing, and it seems
fine.

Mat

-----Original Message-----
From: Vivek Khera [mailto:khera@kcilink.com]
Sent: Friday, 18 October 2002 11:51 PM
To: Matthew Watson
Cc: rt-users@lists.fsck.com
Subject: Re: [rt-users] Slow ticket creation with postgres?

“MW” == Matthew Watson mwatson@netspace.net.au writes:

MW> Any hints as to how to speed this up?

How big is your DB? How much SHM did you allow Postgres to use? Did
you “vacuum analyze” your tables recently (or frequently)?

It is plenty fast for us.

I just need to get around to purging the dead tickets… laziness
keeps me from doing it.


Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.394 / Virus Database: 224 - Release Date: 3/10/2002

Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.394 / Virus Database: 224 - Release Date: 3/10/2002