After a few RT installs, I conclude that I’ve never seen RT running fast.
I am running RT in test on a 64-bit system where most things including
Postgresql run quickly, but RT makes things look rather ordinary, which is
pretty disappointing. I have been poking about in the Aegis stuff for RT
2.1 and it looks like maybe Jesse is working on these aspects… anyone
running bleeding edge who can comment?
Dan Shearer
Open Source Manager
Tel: +61 8 8130 3104
dan@tellurian.com.au
|+ I am running RT in test on a 64-bit system where most things including
|+ Postgresql run quickly, but RT makes things look rather ordinary, which is
|+ pretty disappointing. I have been poking about in the Aegis stuff for RT
|+ 2.1 and it looks like maybe Jesse is working on these aspects… anyone
|+ running bleeding edge who can comment?
I can’t comment on the 2.1 branch, but as for 2.0, we see no speed
issues. Our database has about 5k tickets, with about 60 new tickets
being created weekly now. The number of new tickets weekly was once in
the 200s, but that has change. Nevertheless, RT runs quick for us. We do
not see slowdowns on ticket searches, updates, etc.
We run RT on an P3-550 with 512MB of ram running FreeBSD 4.5.
Our database server is a P3 1Ghz, with 2GB of ram running FreeBSD 4.5 and
MySQL. We have other applications hitting our database at the same time
(billing, apache traffic information, dns stuff), and have yet to see a
real issue. There are various tweaks you can make to your DB of choice to
improve speed.
-darrin
I wouldn’t really expect to see slowdowns with that many tickets,
especially when the database server is pretty beefy for the job.
I’m runnin with about 350k tickets, and putting in a couple of
hundred a DAY,With about 20-30 users. 90% of the slowdows I see
are from large queries being run, which in turn makes updates
running after them lock the tables, which makes queries being run
after that stall waiting for the unlock… and no index seems to
work.
Any comment jeese on how innodb tables would go with the
current release of RT2??
Mat.
Any comment jeese on how innodb tables would go with the
current release of RT2??
Try it on your backup database server (or just a highend desktop box) and see.
I’m sure folks would love to hear a report about how it feels. I’ve only
done work with InnoDB and 2.1
Mat.
http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.
“m” == mwatson writes:
m> are from large queries being run, which in turn makes updates
m> running after them lock the tables, which makes queries being run
m> after that stall waiting for the unlock… and no index seems to
A prime reason to move to Postgres. The concurrency is much better
since it does row-level locking, and a select query doesn’t block an
insert query and vice versa (except when you explicitly lock the
table).
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera@kciLink.com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
Yeah, i’ve attempted to move to postgres, but found some
very odd things happening. I’m about to try some things on
a test machine i’ve got, firstly trying innodb tables with
the current version of rt. should be interesting.
I will also test postgres again (last time I did it , it was at
5am… so perhaps I was just imagining things).
How do you find postgres goes with rt2, the main issue i found
was that it was wrapping every query in a transaction, which
I assume would so things down somewhat. Also I found when
loading the page for a new ticket, rt was generating several
hundred queries…! not sure why.
Mat