No multithreading?

RT Developers
1

We run rt 3.0.10 on perl 5.8.3, apache 2 w/fastcgi

Now that we are as many as 4 people using this server, we figured that
we should upgrade it to improve performance. So we put in another CPU
and more ram.

Dual P3 800Mhz
1.2GB ram

Now, this works great! As long as only one of us work at a time.

Whenever two of us does something at the same time we get errors all
over the place. This leads me to believe that something is not thread
safe… Any leads on this?

Would it help to increase the timeout? 30 sec is a lot tho…

-HK

This is from the apache error log:
[Thu May 13 09:34:10 2004] [error] [client 195.159.151.118] FastCGI:
comm with server “/usr/rt3/bin/mason_handler.fcgi” aborted: idle timeout
(3 0 sec), referer: http://rt.isphuset.no/Search/Listing.html
[Thu May 13 09:34:10 2004] [error] [client 195.159.151.118] FastCGI:
incomplete headers (0 bytes) received from server
“/usr/rt3/bin/mason_handl er.fcgi”, referer:
http://rt.isphuset.no/Search/Listing.html
[Thu May 13 09:35:12 2004] [error] [client 193.12.247.247] FastCGI: comm
with server “/usr/rt3/bin/mason_handler.fcgi” aborted: idle timeout (30
sec), referer:
http://rt.isphuset.no/Search/Listing.html?ValueOfStatus=new&StatusOp=%3D&QueueOp=%3D&ValueOfQueue=8&RowsPerPage=50&NewSearch=1
[Thu May 13 09:36:07 2004] [error] [client 193.12.247.247] FastCGI: comm
with server “/usr/rt3/bin/mason_handler.fcgi” aborted: idle timeout (30
sec), referer:
http://rt.isphuset.no/Search/Listing.html?ValueOfStatus=new&StatusOp=%3D&QueueOp=%3D&ValueOfQueue=8&RowsPerPage=50&NewSearch=1
[Thu May 13 09:36:10 2004] [error] [client 195.159.151.118] FastCGI:
comm with server “/usr/rt3/bin/mason_handler.fcgi” aborted: idle timeout
(3 0 sec), referer: http://rt.isphuset.no/Search/Listing.html
[Thu May 13 09:36:10 2004] [error] [client 195.159.151.118] FastCGI:
incomplete headers (0 bytes) received from server
“/usr/rt3/bin/mason_handl er.fcgi”, referer:
http://rt.isphuset.no/Search/Listing.html
[Thu May 13 09:39:49 2004] [error] [client 195.159.151.118] FastCGI:
comm with server “/usr/rt3/bin/mason_handler.fcgi” aborted: idle timeout
(3 0 sec), referer: http://rt.isphuset.no/Search/Listing.html
[Thu May 13 09:39:49 2004] [error] [client 195.159.151.118] FastCGI:
comm with server “/usr/rt3/bin/mason_handler.fcgi” aborted: idle timeout
(3 0 sec), referer: http://rt.isphuset.no/Ticket/Display.html?id=531

2

[Thu May 13 09:34:10 2004] [error] [client 195.159.151.118] FastCGI:
comm with server “/usr/rt3/bin/mason_handler.fcgi” aborted: idle timeout
(3 0 sec), referer: http://rt.isphuset.no/Search/Listing.html

You probably need to add “-idle-timeout 3600” to your FastCgiServer
directive if it isn’t already there.

HTH,
Michael
Michael S. Liebman m-liebman@northwestern.edu
http://msl521.freeshell.org/
“I have vision and the rest of the world wears bifocals.”
-Paul Newman in “Butch Cassidy & the Sundance Kid”

3

You should also try running more fcgi processes. The default number of
processes is something silly like 1 process. In this case each request
is going to be waiting for previous N requests to finish. Run more and
you should see a fair bit better performance.

I was running on a single cpu P3/700 for quite a while. We had around
10 people using RT and almost never saw timeout issues; the few times
we did were when people tried to view very big tickets that took more
then 30seconds to display.

Eg:
FastCgiServer -processes <4|6|N>

Also unless you are using the perl based process manager [which you
surely aren’t since I don’t think I ever submitted it to jesse] you
will also want to delay how quickly each process starts up. Initing
a fcgi process is fairly expensive.

Eg:
FastCgiServer -processes --init-start-delay

I think I have my delay set to either 30 or 45 seconds.

Matt