Performance issues with reply

RT Users
1

Using:
RT-3.0.9
Apache-1.3.29
modperl-1.29
HTML::Mason-1.25

We recently transitioned from RT-2.0.13 to RT-3.0.9. At the same time
we moved from a dual 450MHz machine with 512MB RAM to a 2.2GHz machine
with 1GB RAM. The move resulted in an overall decrease in
performance. I’ve read some other postings on this list that suggest
our experience is not unique. We are using a Postgres database backend
(resides on the same box as the web server). We have done some
database tuning and logging and I’m pretty confident that the database
is not the cause of the problem.

The action that seems to have the greatest delay is when replying to a
ticket. I enabled MasonX::Profiler to find where in the building of
the reply page the delay is occurring. It is pretty obvious that the
bulk of the delay is in /Elements/SelectOwner, which takes 7-8 seconds
to complete.

In our config there are 11 privileged users. However, the users table
in the database contains 5579 records. There are 15735 tickets in the
database. So I am assuming that when creating the Owner selection box
it is looping through all 5500+ user records to find which ones need to
be put in the list, thus explaining the 7-8 seconds it takes to
complete that component.

This procedure appears to be based on DBIx::SearchBuilder. I did
upgrade that to the newest version with no improvement. I have not yet
tried moving to RT-3.0.10.

Is there anything that can be done to improve the efficiency of this
operation?

Steve

Steven Saner ssaner@hubris.net Voice: 316-858-3000
Director of Network Operations Fax: 316-858-3001
Hubris Communications http://www.hubris.net

2

The action that seems to have the greatest delay is when replying to a
ticket. I enabled MasonX::Profiler to find where in the building of
the reply page the delay is occurring. It is pretty obvious that the
bulk of the delay is in /Elements/SelectOwner, which takes 7-8 seconds
to complete.

You don’t say whether you’re using MySQL or Postgres. But 3.0.11
includes a pretty serious performance fix for Elements/SelectOwner. I
bet that will solve your problem.

3

The action that seems to have the greatest delay is when replying to a
ticket. I enabled MasonX::Profiler to find where in the building of
the reply page the delay is occurring. It is pretty obvious that the
bulk of the delay is in /Elements/SelectOwner, which takes 7-8 seconds
to complete.

You don’t say whether you’re using MySQL or Postgres. But 3.0.11
includes a pretty serious performance fix for Elements/SelectOwner. I
bet that will solve your problem.

We are using Postgres 7.4.2. Are you recommending 3.0.11? I don’t see
that anywhere. Did you mean 3.1.11?

Steve

Steven Saner ssaner@hubris.net Voice: 316-858-3000
Director of Network Operations Fax: 316-858-3001
Hubris Communications http://www.hubris.net

4

You don’t say whether you’re using MySQL or Postgres. But 3.0.11
includes a pretty serious performance fix for Elements/SelectOwner. I
bet that will solve your problem.

We are using Postgres 7.4.2. Are you recommending 3.0.11? I don’t see
that anywhere. Did you mean 3.1.11?

Nope, I mean the next release of 3.0, which is due out soon.

5

Steven Saner wrote:

The action that seems to have the greatest delay is when replying to a
ticket. I enabled MasonX::Profiler to find where in the building of
the reply page the delay is occurring. It is pretty obvious that the
bulk of the delay is in /Elements/SelectOwner, which takes 7-8 seconds
to complete.

You don’t say whether you’re using MySQL or Postgres. But 3.0.11
includes a pretty serious performance fix for Elements/SelectOwner. I
bet that will solve your problem.

We are using Postgres 7.4.2. Are you recommending 3.0.11? I don’t see
that anywhere. Did you mean 3.1.11?
IMHO he means upcoming 3.0.11 minor release. You can wait for it or get
current code right now from SVN, but it’s not even in RC state yet.

		Best regards. Ruslan.
6

Is it somehow possible to have access through web to the repository?
It was very usefull to see what changes are between the versions.

Thanks

SAmuelFrom: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: Monday,03 May,2004 19:05
To: Steven Saner
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Performance issues with reply

You don’t say whether you’re using MySQL or Postgres. But 3.0.11
includes a pretty serious performance fix for Elements/SelectOwner.
I bet that will solve your problem.

We are using Postgres 7.4.2. Are you recommending 3.0.11? I don’t see
that anywhere. Did you mean 3.1.11?

Nope, I mean the next release of 3.0, which is due out soon.

Steve

–

Steven Saner ssaner@hubris.net Voice: 316-858-3000
Director of Network Operations Fax: 316-858-3001
Hubris Communications http://www.hubris.net

http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

RT Developer and Administrator training is coming to LA, DC and Frankfurt this spring and summer.
http://bestpractical.com/services/training.html

Sign up early, as class space is limited.

7

Is it somehow possible to have access through web to the repository?
It was very usefull to see what changes are between the versions.

Unfortunately, all of the available web interfaces to subversion appear
to corrupt our repository with frightening regularity. You can access
the repository using anonymous subversion to

svn://svn.bestpractical.com/rt/