You’re on crack. I’ve got a system with about 50,000 tickets in it and
it runs very fast.
If you knew anything about the code, you’d know the bulk of the speed
issues derive from the backend database, not RT itself. Perhaps you are
having issues there, or your database is not optimized.
Not to flame you, but that msg is the most ignorant comment about a piece
of software I’ve seen in ages.
Admittedly, there are ways RT and the database backend could be
accelerated, but discuss those with knowledge of how algorithms and
systems actually work. Look at the code, ask questions, and offer
suggestions, but don’t complain about it.
Throwing hardware at the problem was probably your first mistake. If a 2
CPU, RAID, 512MB system is ‘slow’ then you’ve got serious problems. If
you had bothered to ask the list, you’d know that RT2 can run just fine on
plain old single CPU/IDE systems. I use a PIII 700 with IDE and over
50,000 tickets and 30 users and it works great.
I’m sorry, but it’s people like you who give IT professionals a bad name.
Go to school or read a book and learn something about your profession.
Til then, you’d probably be better off lurking humbly on maillists such as
these than displaying your ignorance with such panache.
David C. Troy [firstname.lastname@example.org] 410-544-6193 Sales
ToadNet - Want to go fast? 410-544-1329 FAX
570 Ritchie Highway, Severna Park, MD 21146-2925 www.toad.netOn Tue, 20 Aug 2002, Maren S. Leizaola wrote:
Much regretably I’ve had to pull RT2 out. For us even a machine
with 2 cpus, raid, 512MB RAMwith 5000 tickets in the database (99% of
which were closed) the system would take ages to refresh the display. As
it was costing us more on having to wait for the pages to refresh and do
maintenance on it than the time required of handlign all e-mail manually.
I think we are now in a much better position with our e-mail support
without using RT than with RT.
I know it easy to come into a mailing list and piss over someone elses
hard work, however I feel that RT is going has been going in the wrong
direction. Anyway I think the Jesse and everyone else is well aware of
this issue so why go on. Well do for what you have done even though it
is not very strong in the performance area.
I would really like to find some “light” ticketing system where the front
end is PHP based where deamons do not eat up 62MB of RAM or more… I
don’t need all the fancy stuff that RT2 has. A spec like RT1, with
atachments and being able to display chinese characters would be all we
Can someone recommend something light and fast for a very small work
Anyway cheers, I hope RT2 becomes usable in the future.
rt-users mailing list
Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm