OK, I fixed this. I didn't have the jsmin binary, nor did I have it
configured in RT. Problem solved.
Thanks for the pointers. Happy now!
Dave
2011 Training: http://bestpractical.com/services/training.html
On Wed, Aug 03, 2011 at 08:56:14AM -0400, Dave Pascoe wrote:
OK, I fixed this. I didn't have the jsmin binary, nor did I have it
configured in RT. Problem
solved.
Thanks for the pointers. Happy now!
As mentioned in
http://issues.bestpractical.com/Ticket/Display.html?id=17673
If you
Sorry for the delay in responding to this. I have been away and distracted.
I enabled MasonX::Profiler but can't figure out where the debug info gets
written.
Trying to get to the bottom of what exactly is slow because it is bad enough
that it destroys my workflow.
Dave
On Mon, Jul 25, 2011
Hi,
For every web request you should see a profile dumped to stderr. If
it's a standalone server then it's dumped into console. If it's apache
then into apache's error log. This profile shows which components take
more time to run.
On Tue, Aug 2, 2011 at 11:07 PM, Dave Pascoe davek...@gmail.com
Hello Jeffry
Due to your really large RT Environment...
I have tested
rt 4.0.0.1
and rt 3.8.9
only with a few user and tickets ..
maybe rt 4 can handle large rt instances much better than rt 3.8.8 and by
the othe one is vice versa?
so if this isn't the case could you post your config
On Wed, Jul 27, 2011 at 6:46 AM, Jeff Fearn jfe...@redhat.com wrote:
On 07/26/2011 11:32 PM, Kevin Falcone wrote:
I'll note that on a system with 25K users, that page takes about .3 to
render for me (without switching to autocomplete). The owner list is
less concerned with User size and more
On 07/27/2011 06:38 PM, john s. wrote:
Hello Jeffry
Due to your really large RT Environment...
I have tested
rt 4.0.0.1
and rt 3.8.9
only with a few user and tickets ..
maybe rt 4 can handle large rt instances much better than rt 3.8.8 and by
the othe one is vice versa?
so if this isn't
On 07/26/2011 11:32 PM, Kevin Falcone wrote:
On Tue, Jul 26, 2011 at 10:29:19AM +1000, Jeff Fearn wrote:
On 07/26/2011 02:34 AM, Adam Thompson wrote:
Set($AutocompleteOwners, 1);
Compare the display time Tickets-New Search
With AutocompleteOwners: Time to display: 0.442697
Without
On Sat, Jul 23, 2011 at 12:05:37AM -0400, Dave Pascoe wrote:
I would love to learn what you find. I am also experiencing slowness with
4.0.1 compared to
3.8.x. Very noticeable - page turnaround time at least 2-3 seconds longer,
and sometimes
longer than that. Relevant part of my
hello dave
thats the point why i finally decided to use rt 3.8
i have an config with fcgid on my rt 4.0 system
. could someone from the devs say any words to this speeding issue
which we could verify each other ?
and if this the normal state... why i should sacrifice so much more
I can't speak for the dev team, but I have noticed a distinct trend:
Apache+mod_perl is very slow with RT4.0.
Lighttpd+FCGI is fast with RT4.0.
Standalone PSGI is really fast with RT4.0 (but not very scalable unless
you know what you're doing).
I haven't tested Apache with anything other than
: Monday, 25 July, 2011 7:34:27 PM
Subject: Re: [rt-users] Tuning RT4
I can't speak for the dev team, but I have noticed a distinct trend:
Apache+mod_perl is very slow with RT4.0.
Lighttpd+FCGI is fast with RT4.0.
Standalone PSGI is really fast with RT4.0 (but not very scalable unless
you know
On Mon, Jul 25, 2011 at 11:34:27AM -0500, Adam Thompson wrote:
I haven't tested Apache with anything other than mod_perl, so I don't know
if it's Apache-specific or mod_perl-specific.
It's unlikely to be Apache-specific, as we run multiple RT 4.0.1s
without this issue on Apache.
(And yes, I
On Mon, Jul 25, 2011 at 07:54:54PM +0300, Alex Rhys-Hurn wrote:
The php.info and other apache status pages, and webmin that I have running
on this machine are
superfast, so I point to RT as being the culprit.
php.info and the apache status pages are not actually performance
tests since
! It was set to 256meg Ouch!
Sorry about that.
Alex
- Original Message -
From: Kevin Falcone falc...@bestpractical.com
To: rt-users@lists.bestpractical.com
Sent: Monday, 25 July, 2011 8:20:03 PM
Subject: Re: [rt-users] Tuning RT4
On Mon, Jul 25, 2011 at 07:54:54PM +0300, Alex
On 07/26/2011 02:34 AM, Adam Thompson wrote:
I can't speak for the dev team, but I have noticed a distinct trend:
Apache+mod_perl is very slow with RT4.0.
Lighttpd+FCGI is fast with RT4.0.
Standalone PSGI is really fast with RT4.0 (but not very scalable unless
you know what you're doing).
I
I would love to learn what you find. I am also experiencing slowness with
4.0.1 compared to 3.8.x. Very noticeable - page turnaround time at least
2-3 seconds longer, and sometimes longer than that. Relevant part of my
Apache config:
DocumentRoot /usr/local/rt4/share/html
Hello All
from my point of view
Actually we use rt 3.8 in prod environment and the new rt 4.0 in labor
environment
the 3.8 speeds up like an local installed program ...very fast
the 4.0.0 is not so fast as 3.8 but it is acceptable
Neverthless i would like to know why is it that
hello guys
in this thread there are only recommendations for the old module modperl
...
why? is the fcgif module not so performant ... as the modperl module?
best regards john
--
View this message in context:
http://old.nabble.com/Tuning-RT4-tp32056508p32067302.html
Sent from the
Hi,
I have a huge(2M Tickets, ~500 tickets/day) 3.8.1 RT installation and
I'm trying to upgrade to 4.0.1.
I'm facing some performance problems on my staging server(it's almost
the same spec as my production server).
I'm using on 3.8.1:
Alias /rt/ /opt/rt3/share/html/
Directory
On Wed, Jul 13, 2011 at 11:42 PM, Wagner Sartori Junior
wsart...@gmail.com wrote:
The question is: How can I assign the Mason variables(StaticSource,
BufferSize, Preloads, ...) on RT4?
In RT4 and 3 as well you can use the following option in the config to
set mason's properties:
21 matches
Mail list logo
