This is written by our web-admin and Postgres DBA, Rafael Martinez, which
is not a member of this list, and forwarded to me:
We are having performance problems in our RT (3.2.1) installation.
If we try to display a ticket with a long history, it takes many
seconds before the webside is generated. (Ticket/Display.html?id=).
In some browsers (f.ex.IExplorer) the webside is not show until the
browser gets all the data.
The server is not busy and has plenty of idle resources.
We do not have problems with the database. It is not busy at all. Not
IO problems either.
apache uses 100% of cpu when Ticket/Display.html?id= is executed.
If we run strace, can we see a lot of “time(NULL)=xxxxxxxx” system
calls, in our case, around 86000. 177 sql queries are send to the
database and it takes 20 seconds between the first and the last sql
query are send to the database.
It looks like apache is in some idle/loop stage (time(NULL)=xxxxxxxx)
between sending and receiving data to/from the database.
Red Hat Enterprise Linux WS release 3 (Taroon Update 4).
2 x Intel® Xeon™ CPU 2.40GHz.
2 x scsi 36GB 15K (raid 1)
We are running the webserver and the database in the same server.
Database: PostgreSQL 7.3.5
Webserver: apache RH version: httpd-2.0.46-44.ent with
Anyone with the same problem?
Rafael Martinez, email@example.com
Center for Information Technology Services
University of Oslo, Norway
The problem is that our customer complains about the time it takes to load
a long ticket history, and this is a “show-stopper” for us. The latest
version of DBIx::SearchBuilder is also installed.
Tomas A. P. Olaj, email: firstname.lastname@example.org, web: folk.uio.no/tomaso
University of Oslo / USIT (Center for Information Technology Services)
System- and Application Management / Applications Management Group