[rt-users] Upgrade to 3.6.6, slow loading time

[Dominic Lepiane]

We sortof have everything setup the way we want in terms of permssions and such so I don't really want to cause too much havoc on that front.

As for the database side, we have made some changes like:

[mysqld]
set-variable = innodb_buffer_pool_size=2048M
set-variable = innodb_additional_mem_pool_size=512M

Yet still some queries seem to take a really long time.  Using "show processlist" for mysql, I noticed these couple of queries running there at 18s:

1118    rt_user         localhost       rt3     Query   18      User lock       SELECT GET_LOCK('Apache-Session-b9349177d4d8e96cac68dfde36a6e0e5', 3600)
1119    rt_user         localhost       rt3     Query   18      Copying to tmp table    SELECT DISTINCT main.* FROM Users main CROSS JOIN ACL ACL_4 JOIN Principals Principals_1  ON ( Princ


This seems to agree that the issue is *related* to permissions.  Could this possibly be a deadlock problem or something like that?  I'm really reaching now (in case you couldn't tell)... Are there other tuning options I can change for the dbms or possibly other things like adding some other indexes?

Any troubleshooting advice at this point greatly appreciated.

Dominic Lepiane


> -----Original Message-----
> From: Kenneth Crocker [mailto:KFCrocker at lbl.gov]
> Sent: Wednesday, April 09, 2008 1:24 PM
> To: Dominic Lepiane
> Cc: rt-users at lists.bestpractical.com
> Subject: Re: [rt-users] Upgrade to 3.6.6, slow loading time
>
> Dominic
>
>
>         Check your privileges. If you have allowed global
> groups (Everyone,
> Privileged) a lot of ticket ownership & modify privileges,
> that will create a dramatic effect on how long it takes to
> load a ticket. I've found that the more users that have
> privileges to tickets in a queue, the longer it takes to load
> a ticket. Of course, it could also be some DB thing as well.
>
>
> Kenn
> LBNL
>
> On 4/9/2008 1:05 PM, Dominic Lepiane wrote:
> >> -----Original Message-----
> >> Sent: Wednesday, April 09, 2008 12:34 PM
> >> To: rt-users at lists.bestpractical.com
> >> Subject: [rt-users] Upgrade to 3.6.6, queue tickets have
> broken links
> >>
> >> Dear RT Users,
> >>
> >> I have a couple problems so far after having upgraded to RT 3.6.6:
> >> 1 ) The BestPractical logo is a bad link:
> >> img src="//NoAuth/images//bplogo.gif"
> >> 2 ) If I click on a queue, all the tickets returned in that search
> >> are bad links like this:
> >> a href="//Ticket/Display.html?id=60428"
> >
> > ... Snip
> >
> > The answer was, naturally, PEBCAK.  I had the WebPath set
> to "/" instead of "".
> >
> > However, I have noticed that many pages, like if I go to a
> specific ticket, still take a very long time to load. ~10s.
> This is a dual-Xeon-hyper-threaded 3.0 GHz box running RHEL 5
> x86_64 with 4GB RAM, so opening a ticket should not take this
> long.  What have I done wrong this time?
> >
> > Thanks in advance for any advice,
> >
> > Dominic Lepiane
> > _______________________________________________
> > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> >
> > Community help: http://wiki.bestpractical.com Commercial support:
> > sales at bestpractical.com
> >
> >
> > Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> > Buy a copy at http://rtbook.bestpractical.com
> >
>
>