Hi Dimitri and W,
Here is my IOSTAT output..
Device: rrqm/s wrqm/s r/s w/s rMB/s wMB/s avgrq-sz
avgqu-sz await svctm %util
sda 0.02 28.15 1.44 0.25 0.16 0.11 324.94
0.12 72.83 3.69 0.62
sdb 0.01 1.18 0.95 0.88 0.09 0.01 109.57
0.02 13.18 3.41 0.62
dm-0 0.00 0.00 0.00 0.00 0.00 0.00 8.00
0.00 91.41 14.42 0.01
dm-1 0.00 0.00 0.01 0.13 0.00 0.00 9.80
0.00 28.22 7.95 0.11
dm-2 0.00 0.00 0.01 0.55 0.00 0.00 8.36
0.04 78.18 4.57 0.25
dm-3 0.00 0.00 0.91 1.35 0.09 0.01 85.74
0.09 41.36 1.49 0.34
dm-4 0.00 0.00 0.03 0.04 0.00 0.00 14.90
0.01 71.61 2.61 0.02
dm-5 0.00 0.00 1.46 28.40 0.16 0.11 18.37
0.18 6.06 0.21 0.62
I'm using fastcgi right now. I do get an error about wrong python version
in my httpd logs, could that have anything to do with it?
[Thu Dec 29 08:52:23 2011] [notice] FastCGI: process manager initialized
(pid 16291)
[Thu Dec 29 08:52:23 2011] [error] python_init: Python version mismatch,
expected '2.6.5', found '2.6.6'.
[Thu Dec 29 08:52:23 2011] [error] python_init: Python executable found
'/usr/bin/python'.
[Thu Dec 29 08:52:23 2011] [error] python_init: Python path being used
'/usr/lib64/python26.zip:/usr/lib64/python2.6/:/usr/lib64/python2.6/plat-linux2:/usr/lib64/python2.6/lib-tk:/usr/lib64/python2.6/lib-old:/usr/lib64/python2.6/lib-dynload'.
[Thu Dec 29 08:52:23 2011] [notice] mod_python: Creating 4 session mutexes
based on 128 max processes and 0 max threads.
[Thu Dec 29 08:52:23 2011] [notice] mod_python: using mutex_directory /tmp
[Thu Dec 29 08:52:23 2011] [notice] Apache/2.2.15 (Unix) DAV/2
mod_fastcgi/2.4.6 mod_ssl/2.2.15 OpenSSL/1.0.0-fips mod_python/3.3.1
Python/2.6.6 PHP/5.3.3 SVN/1.6.11 configured -- resuming normal operations
We have between 10 and 20 users between instances on each Trac instance.
Would moving to postgres provide a huge benefit?
Check list to compare with my setup:
- which db? I use PostgreSQL 8.4.9
- which Apache/Python connection? I use mod_wsgi
- how many tickets do you have? I have < 1000 per project
- what about local templates? I have almost nothing
I'm using sqlite3 as my database. I'm using fastCGI for my Python/Apache
connection and we do have a local template that we use.
@W - Nice try with the Debian comment. Redhat/Fedora all the way! :-)
Joseph P Villa,
USGS Golden Colorado Geologic Hazards Team,
Linux/UNIX Systems Administrator
1-303-273-8495
"Really? Windows improved that much? Maybe I should give it a try. Do you
still have to type "win" at the prompt after booting up?"
From:
Dimitri Maziuk <[email protected]>
To:
[email protected]
Date:
12/29/2011 12:22 PM
Subject:
Re: [Trac] Trac slowness with version 0.12 on RHEL
Sent by:
[email protected]
On 12/29/2011 01:08 PM, Joseph P Villa wrote:
> I'm using Sqlite3 and I have a RAID 5 setup on my server.
If you're using mdadm on sata drives, run iostat -mx and look at wait
times. Also check for sata resets in /var/log/messages.
You might want to move to postgres, esp. if you have more than a handful
of users.
You might want to tweak your mod_wsgi settings and/or try fastcgi
instead...
There's lots of pieces to this puzzle besides what you can see in
firebug. I'd first look at i/o speeds even if your raid is on an
"enterprise-level" hardware scsii controller.
--
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
[attachment "signature.asc" deleted by Joseph P Villa/GD/USGS/DOI]
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en.
