SelectOwner Extremely slow

I have been experiencing some staggering slow downs in RT. Specifically
in the Ticket Search Build page and the New Ticket page.

I did not experience this on our test server, but once into the
production environment, this problem began to show. When SelectOwner
Element is used, loading a new ticket page or Ticket Search Build can
take upwards of 3 minutes. Commenting the line out that calls that
element, knock the time down to 1 second or less. So this IS the
culprit. There is no doubt.

So using my nifty comment method I tracked the issue down to this
particular area of the element.

foreach my $object (@objects) {
my $Users = RT::Users->new($session{CurrentUser}
$Users->WhoHaveRight(Right => ‘OwnTicket’, Objec
while (my $User = $Users->Next()) {
$user_uniq_hash{$User->Id()} = $User;
}
This loop hangs up my system for minutes on end and effecting the
multi-user environment, plus preventing searches I might add.

So, anyone have any ideas on why such a heavy load and what can be done
to fix it.

I am using rt 3.4.0
Fedora
FastCgi
Perl 5.83
Oracle 10i
2ghz, 2 processor Pentium Zeon with 1gb ram

Also table record counts:
Users: 809
GROUPMEMBERS: 9400
GROUPS: 14731 – This one seems very high since there are only 15
groups in my system aside from the regular CC, AdminCC roles etc…
PRINCIPALS 15500
TICKETS: 3400

Any Ideas here?

Thanks,
-Anthony

Anthony Meo

At Wednesday 4/6/2005 11:57 AM, Meo, Anthony wrote:

I have been experiencing some staggering slow downs in RT. Specifically
in the Ticket Search Build page and the New Ticket page.

I did not experience this on our test server, but once into the production
environment, this problem began to show. When SelectOwner Element is
used, loading a new ticket page or Ticket Search Build can take upwards of
3 minutes. Commenting the line out that calls that element, knock the
time down to 1 second or less. So this IS the culprit. There is no doubt.

There was some discussion of this on the list a month or so back - it
seemed to me this had slowed down considerably in the 3.4 releases. Our
solution has been to replace the drop-down list with a text input field.
From a usability standpoint it seemed easier to type in part of a username
than to pick from a very long list.

Steve

Stephen Turner
Senior Programmer/Analyst - Client Support Services
MIT Information Services and Technology (IS&T)

sturner@mit.edu

There was some discussion of this on the list a month or so back - it
seemed to me this had slowed down considerably in the 3.4 releases.

And I thought that I’d committed a patch in the rc series that had
improved it wildly. I’ll go digging later, if nobody beats me to it.

I did a diff on the SelectOwner in my version compared to the most
current and here it is: Doesn’t seem to be a fix here. Is there
somewhere else I should look?

Compare: (<)C:\Documents and Settings\meoa\My
Documents\projects\dev\RT\Default Interface\html\Elements\SelectOwner
(3282 bytes)
with: (>)C:\Documents and
Settings\meoa\Desktop\RT\rt\rt-3.4.1\html\Elements\SelectOwner (3305
bytes)

50d50
< <OPTION <% ($RT::Nobody->Id() == $Default) && “SELECTED” %>
VALUE="<%$RT::Nobody->Id%>"><%$RT::Nobody->Name%>
55d54
<
76a74,75

80a80

            next if ($User->id == $RT::Nobody->id); # skip nobody

here, so we can make them first later
85a86,89

unshift(@users, $RT::Nobody);

Anthony Meo
Partner Integration Engineer
BT Conferencing, Inc.
25 Braintree Hill Park, Suite 200
Braintree, MA 02184
§ 617.801.6636
© 617.429.9356
(f ) 617.801.6604
anthony.meo@btci.com
www.btconferencing.comFrom: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: Wednesday, April 06, 2005 12:29 PM
To: Stephen Turner
Cc: Meo, Anthony; rt-users
Subject: Re: [rt-users] SelectOwner Extremely slow

There was some discussion of this on the list a month or so back - it
seemed to me this had slowed down considerably in the 3.4 releases.

And I thought that I’d committed a patch in the rc series that had
improved it wildly. I’ll go digging later, if nobody beats me to it.

Our
solution has been to replace the drop-down list with a text input
field.
From a usability standpoint it seemed easier to type in part of a
username
than to pick from a very long list.

Steve

Stephen Turner
Senior Programmer/Analyst - Client Support Services
MIT Information Services and Technology (IS&T)

sturner@mit.edu


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

RT Administrator and Developer training is coming to your town soon!
(Boston, San Francisco, Austin, Sydney) Contact
training@bestpractical.com
for details.

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

Ok,

I found this patch in the archives – if you search for subject below.
Question is, can I apply this patch to rt-3.4.0. It seems like this is
for a version prior since this quote from Jesse’s Explanation

“If folks see a speed boost without errors, it’ll make it into 3.4.0.”

RT 3.4 / Postgres / Search UI performance

Thanks,
Anthony MeoFrom: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Meo,
Anthony
Sent: Wednesday, April 06, 2005 1:14 PM
To: Jesse Vincent; Stephen Turner
Cc: rt-users
Subject: RE: [rt-users] SelectOwner Extremely slow

I did a diff on the SelectOwner in my version compared to the most
current and here it is: Doesn’t seem to be a fix here. Is there
somewhere else I should look?

Compare: (<)C:\Documents and Settings\meoa\My
Documents\projects\dev\RT\Default Interface\html\Elements\SelectOwner
(3282 bytes)
with: (>)C:\Documents and
Settings\meoa\Desktop\RT\rt\rt-3.4.1\html\Elements\SelectOwner (3305
bytes)

50d50
< <OPTION <% ($RT::Nobody->Id() == $Default) && “SELECTED” %>
VALUE="<%$RT::Nobody->Id%>"><%$RT::Nobody->Name%>
55d54
<
76a74,75

80a80

            next if ($User->id == $RT::Nobody->id); # skip nobody

here, so we can make them first later
85a86,89

unshift(@users, $RT::Nobody);

From: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: Wednesday, April 06, 2005 12:29 PM
To: Stephen Turner
Cc: Meo, Anthony; rt-users
Subject: Re: [rt-users] SelectOwner Extremely slow

There was some discussion of this on the list a month or so back - it
seemed to me this had slowed down considerably in the 3.4 releases.

And I thought that I’d committed a patch in the rc series that had
improved it wildly. I’ll go digging later, if nobody beats me to it.

Our
solution has been to replace the drop-down list with a text input
field.
From a usability standpoint it seemed easier to type in part of a
username
than to pick from a very long list.

Steve

Stephen Turner
Senior Programmer/Analyst - Client Support Services
MIT Information Services and Technology (IS&T)

sturner@mit.edu


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

RT Administrator and Developer training is coming to your town soon!
(Boston, San Francisco, Austin, Sydney) Contact
training@bestpractical.com
for details.

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

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

RT Administrator and Developer training is coming to your town soon!
(Boston, San Francisco, Austin, Sydney) Contact
training@bestpractical.com for details.

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

Ok,

I found this patch in the archives – if you search for subject below.
Question is, can I apply this patch to rt-3.4.0. It seems like this is
for a version prior since this quote from Jesse’s Explanation

It sure looks like this patch exists in the current source already. Can
you show us what queries RT is generating while in the SelectOwner
widget?

Jesse