How well does RT scale in terms of numbers of tickets ? Consider that
you have a budget for unlimited hardware (we don’t, but just consider),
would we be crazy to think RT could cope with upwards of 250 thousand
tickets ?
Is anyone running an installation with this amount of tickets, and if so
what have you done in terms of tuning/optimisation, and what hardware
are you running on ?
Michael Pye
Unlimited hardware huh? sounds nice 
I’ve got a db of about 700,000 tickets, I’ve been using 2.0.11 for quite
awhile, and apart from a few small issues (searching based on requestor is
quite slow),its
ok. Been messing with 3 for awhile and speed is generally improved for most
things, but
i’ve had a disable some permissions ‘features’ to get speed upto par when
it is looking
for certain rights (see rt-devel archives).
at 250k tickets, and a well turned db you shouldn’t have much of a problem.
as far as optimisation, the biggest kick in the pants for RT that I found
was
turning on mysql4 query caching.
Hardware, database server is an AMD 1800 with SCSI RAUD and 2GB ram,web
server
is a AMD 1800 with 768mb ram.
Regards,
Matt Watson.–On Tuesday, October 28, 2003 10:09 PM +0000 Michael Pye michael@ulimit.org wrote:
How well does RT scale in terms of numbers of tickets ? Consider that you
have a budget for unlimited hardware (we don’t, but just consider), would
we be crazy to think RT could cope with upwards of 250 thousand tickets ?Is anyone running an installation with this amount of tickets, and if so
what have you done in terms of tuning/optimisation, and what hardware are
you running on ?–
Michael Pye
rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-usersHave you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm