[rt-users] httpd speed on rt3

[AJ]

Have you enabled ExtendedStatus in apache and taken a peek at what it is
doing?

Also there is:

<Location /perl-status>
SetHandler perl-script
PerlHandler Apache::Status
PerlSetVar StatusOptionsAll On
Order Deny,Allow
Deny from All
Allow from <your ip>
</Location>

That will show you the Perl config, Memory, Loaded Modules, the stack, etc..

Out of curiosity, as well as CPU, how does the load average and per process
memory consumption on the box look?  Top can give you those, and vmstat can
at least give you an idea if processes are getting blocked for some reason.
Also for linux, the following can give you memory usage for httpd:
perl -pe 's/^(\w+)-(-w+) /hex($2) - hex($1) . " "/e' \
> </proc/`cat <httpd.pidfile>`/maps


I know in mysql there are sort and read buffer memory settings.  If not set
high enough, performance can degrade. 

Mysql 4.0 will do query caching.  Set query_cache_size in the my.cnf.
Problem is that table updates will clear the cache and RT being a
transactional system, the cache may never be used for ticket but may be used
for principal, user, and group lookups


-----Original Message-----
From: rt-users-bounces at lists.bestpractical.com
[mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Palle
Girgensohn
Sent: Tuesday, January 20, 2004 9:06 PM
To: Mike Frazer; Douglas E. Warner; rt-users at lists.fsck.com
Subject: RE: [rt-users] httpd speed on rt3

I use postgresql. And, I did a check as to how much time was spent by 
postgresql handling the queries, and althogh the same question was asked 
over a hundred times, which surely is a bug, postgresql spent around 800 ms 
doing queries. The request tooks six seconds. And, perl waiting for 
postgresql hardly eats CPU, it's a network connection (or in this case unix 
domain socket) waiting for data. Most of the queries where pretty simple, 
only a few took more than a couple of milliseconds.

Perl probably goes into a loop handling this same data it gets more than a 
hundred times, but it hardly eats cycles while waiting for it to come.

As for MySQL, I have no experience, but isn't 4.x much more competent in 
terms of what SQL it handles, compared to 3.x? This perhaps comes with a 
price, a performance penalty? But as I said, I have no experience with 
MySQL, been using postgresql since 1995... :)

Palle

--On tisdag, januari 20, 2004 09.34.46 -0500 Mike Frazer 
<Michael.Frazer at InterCept.Net> wrote:

> Consider that MySQL may not be optimized on the RT3 machine, and what you
> are seeing with Perl is actually just Perl waiting on the records to be
> retrieved.  There are quite a few joins in the SQL queries, so an
> unoptimized database could very well be slowing things down.
>
> In my personal experience, as well, MySQL 3.23.xx always seemed to run
> better for me than did 4.0.xx, regardless of what I did to improve the
> speed.  Maybe it was just me but that was my experience.
>
> -----Original Message-----
> From: Palle Girgensohn [mailto:girgen at pingpong.net]
> Sent: Saturday, January 17, 2004 11:15 PM
> To: Douglas E. Warner; rt-users at lists.fsck.com
> Subject: Re: [rt-users] httpd speed on rt3
>
>
> I'm seeing similar performance problems. Pls check out the thread @
> rt-devel from Jan 15th.
>
> I run fastcgi, so I see the Perl process eating CPU cycles, since you run
> mod_perl, you see the httpd process hogging, since that's where perl
> runs.  It's definitely perl doing some bad stuff.
>
> I've no idea what happens yet, but just wanted to tell you that you're
> not  alone, FWIW. :)
>
> Palle
>
> --On torsdag, januari 15, 2004 21.01.39 -0500 "Douglas E. Warner"
> <dwarner at ctinetworks.com> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I appologize if this has been covered in the past; please let me know if
>> it  has.
>>
>> I'm running a Dual P3/1.26GHz w/ 1G of RAM on Fedora Core 1, with Apache
>> 1.3.29 and mod_perl 1.29 compiled in and MySQL 4.0.17 RPMs, using RT
>> 3.0.8. Viewing tickets seems especially slow.  Most tickets take 8
>> seconds or longer  to load, and one ticket in particular takes about 16
>> seconds.  On my *much*  humbler box running RT2, it takes about half that
>> time.  During this time, it  doesn't appear to be MySQL that's using CPU
>> or disk, but httpd that's hogging  up 100% of one CPU.
>>
>> I'd really appreciate it if anybody has any ideas on how to reduce the
>> load  time for tickets, or what I can do to track down why tickets are
>> taking so  long to display.
>>
>> - -Doug
>>
>> - --
>> Douglas E. Warner    <dwarner at ctinetworks.com>     Network Engineer
>> CTI/PAdotNET         http://ctinetworks.com        +1 717 975 9000
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.2.3 (GNU/Linux)
>>
>> iD8DBQFAB0YDJV36su0A0xIRAgaUAJ4oSNWnu+6/bFqpmBIIacdRsd+UfACgy4gc
>> FQyHgaosDFe1erCgK1Uj6+s=
>> =U52p
>> -----END PGP SIGNATURE-----
>>
>> _______________________________________________
>> rt-users mailing list
>> rt-users at lists.bestpractical.com
>> http://lists.bestpractical.com/mailman/listinfo/rt-users
>>
>> Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm
>
>
>
>
> _______________________________________________
> rt-users mailing list
> rt-users at lists.bestpractical.com
> http://lists.bestpractical.com/mailman/listinfo/rt-users
>
> Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm




_______________________________________________
rt-users mailing list
rt-users at lists.bestpractical.com
http://lists.bestpractical.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm