I am using RT v3.6.0 on RHEL AS 3 with Oracle 9i as the back-end database on a Pentium server with 1GB of RAM. This RT instance is hosting two business applications and there are close to 1200 queues on it.
I am facing an issue with the “QuickSearch” widget on the RT web interface. It was too slow to load causing user login delays and sometimes it doesn’t load at all. So I removed it from the “RT at a glance” page and made it available under a custom section I created on the left side menu. This addressed the login slowness issue much to the delight of most of the end users. However, some users who tend to use “QuickSearch” actively for getting an overview of ticket statistics on queues relevant to them complain that “QuickSearch is too slow”
I am looking for some ways to quicken up (and to justify the nomenclature to the end users ) this widget. Any ideas/suggestions would be appreciated.
Thanks.
PS: I did a search in wiki and lists but didn’t find a case matching the problem I am facing. That’s why I am writing to this list.
I am using RT v3.6.0 on RHEL AS 3 with Oracle 9i as the back-end
database on a Pentium server with 1GB of RAM. This RT instance is
hosting two business applications and there are close to 1200 queues
on it.
I am facing an issue with the “QuickSearch” widget on the RT web
interface. It was too slow to load causing user login delays and
sometimes it doesn’t load at all. So I removed it from the “RT at a
glance” page and made it available under a custom section I created on
the left side menu. This addressed the login slowness issue much to
the delight of most of the end users. However, some users who tend to
use “QuickSearch” actively for getting an overview of ticket
statistics on queues relevant to them complain that “QuickSearch is
too slow”
I am looking for some ways to quicken up (and to justify the
nomenclature to the end users ) this widget. Any ideas/suggestions
would be appreciated.
Thanks.
PS: I did a search in wiki and lists but didn’t find a case matching
the problem I am facing. That’s why I am writing to this list.
I am using RT v3.6.0 on RHEL AS 3 with Oracle 9i as the back-end database on a Pentium server with 1GB of RAM. This RT instance is hosting two business
applications and there are close to 1200 queues on it.
RT 3.6.0 is over 3 years old. We’ve made many, many performance
improvements in the sixteen releases since then. Coming up to a recent RT
is the right first step. Additionally, if you folks have 1200 queues,
I suspect you’ll get a LOT of utility out of upgrading to a more recent
server with more RAM than a $200 netbook.
Just wanted to check if there are any ways to optimize it that I am not aware of.
Indeed, we are planning to migrate it to a dual quad core, 4GB RAM server soon. I will also upgrade RT to the most recent version then.----- Original Message -----
From: Jesse Vincent jesse@bestpractical.com
To: Umasankar Pandurangan
Cc: rt-users@lists.bestpractical.comrt-users@lists.bestpractical.com
Sent: Wed Nov 25 22:42:06 2009
Subject: Re: [rt-users] QuickSearch Too Slow - rt-3.6.0
On Tue 24.Nov’09 at 13:01:39 +0530, Umasankar Pandurangan wrote:
Hi,
I am using RT v3.6.0 on RHEL AS 3 with Oracle 9i as the back-end database on a Pentium server with 1GB of RAM. This RT instance is hosting two business
applications and there are close to 1200 queues on it.
RT 3.6.0 is over 3 years old. We’ve made many, many performance
improvements in the sixteen releases since then. Coming up to a recent RT
is the right first step. Additionally, if you folks have 1200 queues,
I suspect you’ll get a LOT of utility out of upgrading to a more recent
server with more RAM than a $200 netbook.
Just wanted to check if there are any ways to optimize it that I am not aware of.
Indeed, we are planning to migrate it to a dual quad core, 4GB RAM server soon. I will also upgrade RT to the most recent version then.
Hi,
I am using RT v3.6.0 on RHEL AS 3 with Oracle 9i as the back-end database on a Pentium server with 1GB of RAM. This RT instance is hosting two business
applications and there are close to 1200 queues on it.
Depending on how ‘soon’ is you might have your DBA have a look at the
queries logged in the SGA to see if there are any that can be optimised
by using an additional index. I’m on Oracle10g and came from 9i and know
from experience that the optimiser in those versions got a good overhaul
which helped RT quite a bit. Keep in mind though that QuickSearch is
doing lots and lots of small queries so don’t be surprised that your 10x
faster machine only displays this widget 2x faster.
) this widget. Any ideas/suggestions would be appreciated.
) this widget. Any ideas/suggestions