<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.6944.0">
<TITLE>RE: [rt-users] mod_perl vs fastcgi, which performs best,which is more scalable?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2> I've been running on FastCGI since 3.0.7. Starting from 3.0.9 we have seen some horrendous performance problems (CPU pegging and effectively hanging the application for upwards of a minute) even on modern hardware with minimal workloads. We were able to work around them by pre-starting multiple server processes (the perl process is actually what seems to hang), and performance has been pretty good since then.<BR>
I did hear from one mod_perl user who said he had a similar problem, but I've never tried that configuration myself.<BR>
For comparison, I've got a dual Xeon server with 2GB RAM and hardware mirrored SATA drives running RHEL 3.<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: rt-users-bounces@lists.bestpractical.com on behalf of Charles Jones<BR>
Sent: Tue 6/15/2004 5:14 PM<BR>
To: rt-users@lists.bestpractical.com<BR>
Subject: [rt-users] mod_perl vs fastcgi, which performs best,which is more scalable?<BR>
<BR>
I have an associate who has been running RT for quite some time, and has<BR>
literally tens of thousands of tickets in the database. He mentioned<BR>
that sometimes loading a ticket can take an extremly long time (I assume<BR>
if it has other parent/child tickets that it has to find). I do not want<BR>
this to eventually happen to my RT instance, so I am wondering what the<BR>
optimal setup is. He is using mod_perl, I am using fastcgi. His apache<BR>
and mysql are on solaris, mine are on linux. Both architectures are<BR>
SMP, but I really am more interested in optimal setups and tweaks for RT<BR>
on the software side, rather than the OS and hardware. In other words,<BR>
we can probably discuss at length whether apache runs better on a<BR>
multi-proc Solaris box or a Linux box, as well as 64bit Mysql advantages<BR>
etc.<BR>
<BR>
What I am wondering exactly is:<BR>
1. Which performs better in general, mod_perl or fastcgi? I googled for<BR>
some benchmarks and didn't really find anything enlightening.<BR>
2. Is there anything that can be done to the RT database itself, to<BR>
speed up a large database, short of actually deleting older tickets? <BR>
Things like table indexes, ensuring all the numeric tables are numeric<BR>
types, etc?<BR>
3. How aware are the RT developers of issues later down the road when<BR>
the database gets huge? In other words, is RT3 as optimal as it can be<BR>
as far as making the db queries as efficient as possible, or is there a<BR>
lot of work and improvment that can/will be done in future versions?<BR>
<BR>
Thanks,<BR>
-Charles Jones<BR>
_______________________________________________<BR>
<A HREF="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users">http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users</A><BR>
<BR>
RT Developer and Administrator training is coming to LA, DC and Frankfurt this spring and summer.<BR>
<A HREF="http://bestpractical.com/services/training.html">http://bestpractical.com/services/training.html</A><BR>
<BR>
Sign up early, as class space is limited.<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>