Heya all.
Just wondering what kind hardware you run RT on and the number of
users/tickets that supports.
Currently i’m running it on a pair of AMD1800’s with 512mb ram each. with
500,000+ tickets and about 40-50 Staff (about 20-30 using it at one time),
and most of the time speed is fair from snappy. basically wondering if
through more hardware at the mysql server will improve things much?
Regards,
Matthew Watson
Netspace Online Systems
Heya all.
Just wondering what kind hardware you run RT on and the number of
users/tickets that supports.Currently i’m running it on a pair of AMD1800’s with 512mb ram each. with
500,000+ tickets and about 40-50 Staff (about 20-30 using it at one time),
and most of the time speed is fair from snappy. basically wondering if
through more hardware at the mysql server will improve things much?
I’d think memory usage is the bottleneck here. Which version of MySQL
are You using? How long do single requests take? ISTR that You can
append &debug=1 to RT specific URLs to get detailed timings.
Regards,
Harald
To create a new ticket in a queue takes about 10 seconds
To find all the open/new unowed tickets in a given queue 5 seconds
As about but with Requestor LIKE me@mydomain.com = 20 seconds.
Using mysql 3.23.53-log with innodb tables. Probably going to move to
whatever is the latest in the 4 series when I get time.
You think the bottle neck is on the http server or the mysql server? I’m
trying to get our sysadmin department to put some load monitoring on these
machines, if they don’t hurry up i’ll do it myself 
Regards
Matthew Watson.–On Thursday, 3 July 2003 10:13 AM +0200 Harald Wagener hwagener@hamburg.fcb.com wrote:
On Thu, Jul 03, 2003 at 02:47:25PM +0800, Matthew Watson wrote:
Heya all.
Just wondering what kind hardware you run RT on and the number of
users/tickets that supports.Currently i’m running it on a pair of AMD1800’s with 512mb ram each.
with 500,000+ tickets and about 40-50 Staff (about 20-30 using it at
one time), and most of the time speed is fair from snappy. basically
wondering if through more hardware at the mysql server will improve
things much?
I’d think memory usage is the bottleneck here. Which version of MySQL
are You using? How long do single requests take? ISTR that You can
append &debug=1 to RT specific URLs to get detailed timings.Regards,
Harald
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
To create a new ticket in a queue takes about 10 seconds
To find all the open/new unowed tickets in a given queue 5 seconds
As about but with Requestor LIKE me@mydomain.com = 20 seconds.
You should probably test 3.0.4pre1, since jesse said it included two
changes that enhance query speed a lot.
Using mysql 3.23.53-log with innodb tables. Probably going to move to
whatever is the latest in the 4 series when I get time.
List canon seems to be that 4.0.13 (the current stable 4.0 release) is
faster, more stable, and better suited for RT 3.0.x than the 3.23
series.
You think the bottle neck is on the http server or the mysql server?
I’m trying to get our sysadmin department to put some load monitoring
on these machines, if they don’t hurry up i’ll do it myself
You should ask them to log slow queries and forward them to You so they
can be discussed on the list.
Regards,
Harald
You should ask them to log slow queries and forward them to You so they
can be discussed on the list.
Been down that road, I know the slow queries, and haven’t been able to get
any resolution on that. Unfortunately due to the size of our db changing to
RT3.0.x is far from trivial task.
You should ask them to log slow queries and forward them to You so
they
can be discussed on the list.Been down that road, I know the slow queries, and haven’t been able to
get any resolution on that. Unfortunately due to the size of our db
changing to RT3.0.x is far from trivial task.
Ah, You did not state You have RT 2 running, and I implied RT 3 - sorry
about that. The rt2 to rt3 import tool features an incremental mode
which might help You in migrating over an extended time frame.
Regards,
Harald
Arh sorry, thought I mentioned that, yeh 2.0.11, converting to the database
on our testing system is on the plans, but its gonna take about 2 weeks of
converting I think 
Mat.t> On Donnerstag, 3. Juli 2003, at 13:05 Uhr, Matthew Watson wrote:
You should ask them to log slow queries and forward them to You so
they
can be discussed on the list.Been down that road, I know the slow queries, and haven’t been able to
get any resolution on that. Unfortunately due to the size of our db
changing to RT3.0.x is far from trivial task.Ah, You did not state You have RT 2 running, and I implied RT 3 - sorry
about that. The rt2 to rt3 import tool features an incremental mode which
might help You in migrating over an extended time frame.Regards,
Harald
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