My company is going to be making the move to RT3 shortly, having been using
RT2 for some time now.
Our RT2 machine is running Postgres, but has been having some rather severe
performance issues that I’ve been unable to clear up through DB tuning. Ours
is the case where loading a ticket causes Postmaster to consume 100% CPU for
an extended period while loading the ticket - I’ve seen other people mention
this issue on this list but no definite solutions for it.
I’m debating the move from Postgres to MySQL for the RT3 box. I’m wondering
if anyone has experience with either or what the general consensus is in
regard to Postgres vs MySQL (with regard to RT.)
Also, I haven’t yet RTFM, but I’m assuming that there’s some way to migrate
our 12,000+ RT2 tickets to the RT3 system?
Our RT2 machine is running Postgres, but has been having some rather severe
performance issues that I’ve been unable to clear up through DB tuning. Ours
is the case where loading a ticket causes Postmaster to consume 100% CPU for
an extended period while loading the ticket - I’ve seen other people mention
this issue on this list but no definite solutions for it.
I’ve noticed this in the last few days with postgresql 7.3.2 and rt 3.0.0,
when trying to “reply” to a ticket. See my other post today for details.
Having browsed the rt-users and rt-devel lists, I’m not sure if RT 3 is
the right choice right now. Seems like there may still be some pretty
heavy duty performance bugs to sort out. Of course, people tend to only
write to these lists when they’ve got a problem … I should be looking
elsewhere for affirmations and glowing praise.
We had perf. issues with 4000 tickets.
What I did was install rt2.0.15 (I was a 2.0.9) on a faster machine
(p4/2.4GHz w/PC2100 DDR 512MB), along with the latest postgres (7.3.2 I
guess whatever the latest is I got it today).
What sort of performance issues? I’m looking to avoid the postgres 100%
CPU utilization on ticket-display problem that we’re having now. If you
were having that one (which make RT a major PIA sometimes) and it’s gone
now, then I’m tempted to head for RT 2.0.15. Having read about the
similar problem people are having with reply-to tickets consuming
massive CPU in RT3, 2.0.15 sounds like the safer bet.
Apparently doing those three things has yielded a very significant
improvement (everyone is happy now).
This would be good.
The old machine was an athlon 1.1GHz w/1gig SDRAM.
One question - do you do a “vacuum verbose analyze” each night? The verbose
is unnecessary, but you can see how many obsolete tuples it deletes if you
do verbose.
Yup. We’ve got the nightly vacuum in there.
What is you hardware config?
I’m not sure of the processor spec, but it’s probably in the
neighbourhood of a Ghz - 1 Gig of RAM.
What sort of performance issues? I’m looking to avoid the postgres 100%
CPU utilization on ticket-display problem that we’re having now. If you
were having that one (which make RT a major PIA sometimes) and it’s gone
now, then I’m tempted to head for RT 2.0.15. Having read about the
similar problem people are having with reply-to tickets consuming
massive CPU in RT3, 2.0.15 sounds like the safer bet.
I think it isn’t just moving to rt2.0.15 that did it, I think it’s a combo
of the faster hardware (roughly 3x the memory bandwidth, 2x processor
clock adjusted for athlon being faster than p4), latest version of postgres.
ALSO NOTE: I thought everything was fine, then I couldn’t write tickets.
Apparently 2.0.15 is NOT happy with the perl modules you install for 3.0.0.
I’m going to have to redo the installation with the packages that 2.0.9
wanted - and my performance may go away if it was related to new versions
of the perl modules.
Nicolae P. Costescu, Ph.D. / Senior Developer
Stronghold Technologies
46040 Center Oak Plaza, Suite 160 / Sterling, Va 20166
Tel: 571-434-1472 / Fax: 571-434-1478
Having browsed the rt-users and rt-devel lists, I’m not sure if RT 3 is
the right choice right now. Seems like there may still be some pretty
heavy duty performance bugs to sort out. Of course, people tend to only
write to these lists when they’ve got a problem … I should be looking
elsewhere for affirmations and glowing praise.
We have been using RT3 for almost two weeks now and are up to 2300 tickets
as of right now. We haven’t noticed any performance problems. In fact we
have only noticed huge performance increases (compared to RT1.x which is
understandable). We are using MySQL as the DB engine.
