Hello all,
I’m not sure if was the case before the upgrade to 4.0.0 from 3.8.8, but
I’ve noticed intermittent slowdown… particularly on the front page. I have
a suspect as to why this is the case, and I wanted to know if this could be
backed up. The ppl who use rt here requested that “resolved” status be an
active status, so it shows up as a column on the right for the queues, etc…
we’re up to around 7000 tickets, and I’m wondering if the taking of
inventory of all these tickets might be what’s causing the slowdown. At
times I can wait upwards for 20+ seconds while apache churns away at 99.9%
CPU usage, waiting on the front page to generate. Could it be the result of
all the tickets that rt is inventorying to display as active that is the
cause of this?
ok… update… it only seems to do this when I’m going through a proxy
server… odd. I can hit it without any trouble inside our network, and
from the internet, but when it goes through my squid proxy, it wants to
choke out.On Wed, May 18, 2011 at 10:21 AM, Chris Hall hiro24@gmail.com wrote:
Hello all,
I’m not sure if was the case before the upgrade to 4.0.0 from 3.8.8, but
I’ve noticed intermittent slowdown… particularly on the front page. I have
a suspect as to why this is the case, and I wanted to know if this could be
backed up. The ppl who use rt here requested that “resolved” status be an
active status, so it shows up as a column on the right for the queues, etc…
we’re up to around 7000 tickets, and I’m wondering if the taking of
inventory of all these tickets might be what’s causing the slowdown. At
times I can wait upwards for 20+ seconds while apache churns away at 99.9%
CPU usage, waiting on the front page to generate. Could it be the result of
all the tickets that rt is inventorying to display as active that is the
cause of this?
Hi,
Then it’s something about headers your proxy server adds to the request.On Wed, May 18, 2011 at 6:30 PM, Chris Hall hiro24@gmail.com wrote:
ok… update… it only seems to do this when I’m going through a proxy
server… odd. I can hit it without any trouble inside our network, and
from the internet, but when it goes through my squid proxy, it wants to
choke out.
On Wed, May 18, 2011 at 10:21 AM, Chris Hall hiro24@gmail.com wrote:
Hello all,
I’m not sure if was the case before the upgrade to 4.0.0 from 3.8.8, but
I’ve noticed intermittent slowdown… particularly on the front page. I have
a suspect as to why this is the case, and I wanted to know if this could be
backed up. The ppl who use rt here requested that “resolved” status be an
active status, so it shows up as a column on the right for the queues, etc…
we’re up to around 7000 tickets, and I’m wondering if the taking of
inventory of all these tickets might be what’s causing the slowdown. At
times I can wait upwards for 20+ seconds while apache churns away at 99.9%
CPU usage, waiting on the front page to generate. Could it be the result of
all the tickets that rt is inventorying to display as active that is the
cause of this?
Best regards, Ruslan.