Performance problem - RT3.0.3 on Postgresql 7.3.3

Hi all,

Just upgraded to RT 3.0.3, on PostgreSql 7.3.3 (FreeBSD 4.8 box). The database
had already existed (and had RT 3.0.2 running on it), so I just got the
upgrade through the ports collection, and left the existing database intact.
I restarted the postgres server and apache, and that was all…

The performance of the database server is extremely bad when any
Reply/Resolve/Comment is issued on a ticket. Any suggestions?

Thanks much,
Sophie

have you tuned PostgreSQL?

Mine seems(!) to be okay on a UnixWare box.

BTW, Jesse or other devs, you guys are welcome to an account to test new
versions etc on my box.

LER–On Thursday, June 26, 2003 15:28:21 -0400 Sophie Rockhsar sophia@aps.org wrote:

Hi all,

Just upgraded to RT 3.0.3, on PostgreSql 7.3.3 (FreeBSD 4.8 box). The
database had already existed (and had RT 3.0.2 running on it), so I just
got the upgrade through the ports collection, and left the existing
database intact. I restarted the postgres server and apache, and that
was all…

The performance of the database server is extremely bad when any
Reply/Resolve/Comment is issued on a ticket. Any suggestions?

Thanks much,
Sophie


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

Hi Larry,

Using what I had from 3.0.2, I had tuned the “shared_buffers” parameter in the
postgresql.conf file by setting it to 8192. Apart from that, what other
tune-ups would you recommend?

Thanks,
SophieOn Thursday 26 June 2003 03:36 pm, Larry Rosenman wrote:

have you tuned PostgreSQL?

Mine seems(!) to be okay on a UnixWare box.

BTW, Jesse or other devs, you guys are welcome to an account to test new
versions etc on my box.

LER

–On Thursday, June 26, 2003 15:28:21 -0400 Sophie Rockhsar sophia@aps.org wrote:

Hi all,

Just upgraded to RT 3.0.3, on PostgreSql 7.3.3 (FreeBSD 4.8 box). The
database had already existed (and had RT 3.0.2 running on it), so I just
got the upgrade through the ports collection, and left the existing
database intact. I restarted the postgres server and apache, and that
was all…

The performance of the database server is extremely bad when any
Reply/Resolve/Comment is issued on a ticket. Any suggestions?

Thanks much,
Sophie


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Hi Larry,

Using what I had from 3.0.2, I had tuned the “shared_buffers” parameter
in the postgresql.conf file by setting it to 8192. Apart from that, what
other tune-ups would you recommend?
that “should” do it. That’s what I’m using, albeit on a UnixWare box, and
7.3.3
of PG.

Just an idea :slight_smile:

Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

Sophie Rockhsar wrote:

Hi all,

Just upgraded to RT 3.0.3, on PostgreSql 7.3.3 (FreeBSD 4.8 box). The database
had already existed (and had RT 3.0.2 running on it), so I just got the
upgrade through the ports collection, and left the existing database intact.
I restarted the postgres server and apache, and that was all…

The performance of the database server is extremely bad when any
Reply/Resolve/Comment is issued on a ticket. Any suggestions?

Yep, same setup, same issues - excetp mine is a RedHat 7.3
I already discussed it with jesse.

lG uk
Ulrich Kiermayr Zentraler Informatikdienst der Universitaet Wien
Network Security Universitaetsstrasse 7, 1010 Wien, Austria
eMail: ulrich.kiermayr@univie.ac.at Tel: (+43 1) 4277 / 14104
Hotline: security.zid@univie.ac.at Fax: (+43 1) 4277 / 9140
GPG Key fingerprint = BF0D 5749 4DC1 ED74 AB67 7180 105F 491D A8D7 64D8

So, is there anything else to be done, such as adding more indexes, etc.?
Would you please forward to me what Jesse had to say about this?

Thanks,
SophieOn Thursday 26 June 2003 03:48 pm, Ulrich Kiermayr wrote:

Sophie Rockhsar wrote:

Hi all,

Just upgraded to RT 3.0.3, on PostgreSql 7.3.3 (FreeBSD 4.8 box). The
database had already existed (and had RT 3.0.2 running on it), so I just
got the upgrade through the ports collection, and left the existing
database intact. I restarted the postgres server and apache, and that was
all…

The performance of the database server is extremely bad when any
Reply/Resolve/Comment is issued on a ticket. Any suggestions?

Yep, same setup, same issues - excetp mine is a RedHat 7.3
I already discussed it with jesse.

lG uk

Hello RT users,

Just to add another data point, I am using rt-3-0-2 and postgresql-7.3.2 on Red Hat 8, and I am having the exact same issues with Reply/Resolve/Comment. We have a relatively new install of and not a lot of tickets, and it can take 60-70 seconds when clicking on Reply/Resolve/Comment.

I’d love to know any performance tweaks that could be done to Red Hat, RT or PostgreSql…?

Val-----Original Message-----
From: Sophie Rockhsar [mailto:sophia@aps.org]
Sent: Thursday, June 26, 2003 12:28 PM
To: rt-users@lists.fsck.com
Subject: [rt-users] performance problem - RT3.0.3 on Postgresql 7.3.3

Hi all,

Just upgraded to RT 3.0.3, on PostgreSql 7.3.3 (FreeBSD 4.8 box). The database
had already existed (and had RT 3.0.2 running on it), so I just got the
upgrade through the ports collection, and left the existing database intact.
I restarted the postgres server and apache, and that was all…

The performance of the database server is extremely bad when any
Reply/Resolve/Comment is issued on a ticket. Any suggestions?

Thanks much,
Sophie
rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Hi all,

Just to add another data point in here…

We are using Debian, Postgres 7.3.3 and RT 3.0.3 (and all of it’s
dependencies :slight_smile:

If you are in this setup I would suggest that you try the patch that
Christopher Audley wrote and sent to the devel list:

Sent: Wednesday, June 25, 2003 20:46
Subject: [rt-devel] Users::WhoHaveRight and Sybase

Using this patch gave us the following results:
Well, I have tested this and have come up with the following results (all
times are averaged over ten runs):

Page before time after time
Ticket/Create.html 13.6 0.4
Ticket/ModifyPeople.html 9.5 0.6
Search/Bulk.html ~4 ~2

Using the ab tool from Apache gave these results:

old
Document Path: /rt3/Ticket/ModifyPeople.html?id=1502
Document Length: 9951 bytes

Concurrency Level: 1
Time taken for tests: 299.844 seconds
Complete requests: 20

Percentage of the requests served within a certain time (ms)
50% 13132
66% 15160
75% 18217
80% 18981
90% 24829
95% 24829

new
Document Path: /rt3/Ticket/ModifyPeople.html?id=1502
Document Length: 9951 bytes

Concurrency Level: 1
Time taken for tests: 16.553 seconds
Complete requests: 20

Percentage of the requests served within a certain time (ms)
50% 668
66% 677
75% 689
80% 720
90% 1497
95% 1497

As you can see… A distinct improvement!

Hope this helps you all,
Cheers,
Paul

And more importantly :slight_smile: (Given that this is the request that people are
saying is really slow)

This is also from ab:

old:
Document Path: /rt3/Ticket/Update.html?Action=Respond&id=1003
Document Length: 9261 bytes

Concurrency Level: 1
Time taken for tests: 214.115 seconds
Complete requests: 20

Percentage of the requests served within a certain time (ms)
50% 10529
66% 10687
75% 10822
80% 11066
90% 11943

new:
Document Path: /rt3/Ticket/Update.html?Action=Respond&id=1003
Document Length: 9261 bytes

Concurrency Level: 1
Time taken for tests: 18.344 seconds
Complete requests: 20

Percentage of the requests served within a certain time (ms)
50% 796
66% 827
75% 848
80% 891
90% 1018

BTW, just in case anyone out there is using the Debian packages and wants to
install this, here are the steps required:
mkdir -p /usr/local/share/request-tracker3/lib/RT/
cp Groups_Local.pm Users_Local.pm
/usr/local/share/request-tracker3/lib/RT/
mkdir -p /usr/local/share/request-tracker3/html/Elements/
cp SelectOwner.dat
/usr/local/share/request-tracker3/html/Elements/SelectOwner

For the standard RT install you need to do something similar, but I am not
sure what the exact directories are.

BTW (if you are reading this) Thanks to Andrew Stribblehill for the Debian
packages! They have made my life so much easier!

I hope this helps,

Cheers,
Paul

BTW, just in case anyone out there is using the Debian packages and wants to
install this, here are the steps required:
mkdir -p /usr/local/share/request-tracker3/lib/RT/
cp Groups_Local.pm Users_Local.pm
/usr/local/share/request-tracker3/lib/RT/
mkdir -p /usr/local/share/request-tracker3/html/Elements/
cp SelectOwner.dat
/usr/local/share/request-tracker3/html/Elements/SelectOwner

Just a quick note, as co-maintainer of the Debian RT3 package. These
mkdir steps should not be needed now. The latest (3.0.3-1) package
will, during the postinst stage, try to create all the necessary local
directories for you on install/upgrade and give them the correct
ownership and permissions.

BTW (if you are reading this) Thanks to Andrew Stribblehill for the Debian
packages! They have made my life so much easier!

We’re glad to hear that the Debian package of RT3 is appreciated.

Cheers,

Stephen Quinney stephen@jadevine.org.uk

And more importantly :slight_smile: (Given that this is the request that people are
saying is really slow)

This is also from ab:

old:

Document Path: /rt3/Ticket/Update.html?Action=Respond&id=1003
Document Length: 9261 bytes

Concurrency Level: 1
Time taken for tests: 214.115 seconds
Complete requests: 20

Percentage of the requests served within a certain time (ms)
50% 10529
66% 10687
75% 10822
80% 11066
90% 11943

I am just curious about how did you generate an output like that

new:

Document Path: /rt3/Ticket/Update.html?Action=Respond&id=1003
Document Length: 9261 bytes

Concurrency Level: 1
Time taken for tests: 18.344 seconds
Complete requests: 20

Percentage of the requests served within a certain time (ms)
50% 796
66% 827
75% 848
80% 891
90% 1018

Asif Iqbal
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x8B686E08
There’s no place like 127.0.0.1

-----Original Message-----
From: rt-users-admin@lists.fsck.com Behalf Of Asif Iqbal
I am just curious about how did you generate an output like that

Since other people may also be interested…

Apache comes with a program called “ab”, however it has the limitation that
you cannot get it to login. So, using liveHTTPHeaders and Mozilla, I login,
grab the session key and pass it to ab using the -C switch.

The I just do the following (this is all from my linux box, but I am sure
you could do the same under windows/other OS of choice):

ab -C RT_SID=9ac14f4de509e51f7f33def5634fff8a
http://rt/rt3/Ticket/Update.html?Action=Respond&id=1003

and bobs your uncle. The ouput that I sent to the list :slight_smile:

Cheers,
Paul