Hello, all!
I am testing two free ticketing system: RT3 and OTRS.
The first thing I have seen is the different performance
of the two systems. One ticket creation is very fast
in OTRS but in RT3 costs 4 seconds of CPU (i have done some
performance tuning, like example delete all language files
except en and es, with all language files a new ticket costs more than
10 seconds). Both, OTRS and RT3, use Postgres as RDBM and mod_perl.
System:
Pentium 3 with 1 Gb de RAM
SO:
Linux Debian stable.
Postgres 7.2.1
Perl 5.6.1
Apache/1.3.26 with mod_perl
I like more RT3 but I cannot choose it if he is so slow.
Why RT3 is so slow?
Any pointer to tuning?
Best regards,
Agustin
| Jose Agustin Lopez Bueno |
| E-Mail: Agustin.Lopez@uv.es |
| Home Page: Welcome to Agustin's Personal Page |
| http://www.uv.es/postman/ |
| Tfnos: +34-96-3544310 +34-96-3543129 |
| Fax: +34-96-3544200 |
| Servicio de Informatica, Univ. de Valencia, Spain |
System:
Pentium 3 with 1 Gb de RAM
SO:
Linux Debian stable.
Postgres 7.2.1
Perl 5.6.1
Apache/1.3.26 with mod_perl
I like more RT3 but I cannot choose it if he is so slow.
Why RT3 is so slow?
Any pointer to tuning?
You might want to 1) run a current version of postgres and two make sure
you’ve told postgres to use reasonable amounts of memory.
Best regards,
Agustin
–
======================================================
| Jose Agustin Lopez Bueno |
| E-Mail: Agustin.Lopez@uv.es |
| Home Page: Welcome to Agustin's Personal Page |
| http://www.uv.es/postman/ |
| Tfnos: +34-96-3544310 +34-96-3543129 |
| Fax: +34-96-3544200 |
| Servicio de Informatica, Univ. de Valencia, Spain |
rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users
Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.
Hello.
Major feature of RT3 it’s powerful abilities of customisation. And in
some cases perfomance suffer from it.
Agustin.Lopez@uv.es wrote:
Hello, all!
I am testing two free ticketing system: RT3 and OTRS.
The first thing I have seen is the different performance
of the two systems. One ticket creation is very fast
in OTRS but in RT3 costs 4 seconds of CPU (i have done some
performance tuning, like example delete all language files
except en and es, with all language files a new ticket costs more than
10 seconds). Both, OTRS and RT3, use Postgres as RDBM and mod_perl.
I don’t think that ticket creation is major perfomance characteristic of
such systems.
System:
Pentium 3 with 1 Gb de RAM
SO:
Linux Debian stable.
Postgres 7.2.1
Perl 5.6.1
Apache/1.3.26 with mod_perl
I like more RT3 but I cannot choose it if he is so slow.
Why RT3 is so slow?
Any pointer to tuning?
Use latest RT3 also there are have been perfomance tunings in recent
releases.
Also use latest DBIx::SearchBuilder.
Use latest RT3 also there are have been perfomance tunings in recent
releases.
Also use latest DBIx::SearchBuilder.
Actually, DBIx-SearchBuilder 0.92 has a possible performance regression
to fix a bug. Have a shot with 0.90?
Best regards,
Agustin
rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users
Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.
“JV” == Jesse Vincent jesse@bestpractical.com writes:
Use latest RT3 also there are have been perfomance tunings in recent
releases.
Also use latest DBIx::SearchBuilder.
JV> Actually, DBIx-SearchBuilder 0.92 has a possible performance regression
JV> to fix a bug. Have a shot with 0.90?
0.90 returns unsorted result sets with Postgres and RT2. My “last
known working” version is 0.88.
need to dig up time to debug when nobody else is logged in, which is
tough when you’ve got support reps working 24x7 
We’ve discovered that RT 2.0.15 hangs when we try to search for two or more
requestors in the same search query. Does anyone know of a work-around for
this? This brings our server to its knees every time and doesn’t let go
until I kill the process in MySQL.
John DeBerry
John DeBerry wrote:
We’ve discovered that RT 2.0.15 hangs when we try to search for two or more
requestors in the same search query. Does anyone know of a work-around for
this? This brings our server to its knees every time and doesn’t let go
until I kill the process in MySQL.
John DeBerry
It’s fixed in >= 3.0.5 only and noone have ported this fix to 2.0.15.
It’s not one line fix.
So you have to move to 3.x or backport patche to 2.x
Good Luck. Ruslan.