[rt-users] Can RT scale up?

[Matthew Watson]

Sure,

 

 We run a pair of opteron's running at 2.1Ghz, each with 2gb ram. These
act as the web/mail front end for RT (behind a local director).

 

We also run oracle on a sparc ultra-4 with 4gb ram,  this also serves
other applications.

 

The front end is probably a little overkill at the moment, although our
testing showed that on these machines, once you get over about 5-10
simultaneous requests the average delivery time for pages starts to
rise. This gives us a bit of wiggle room (with staff numbers) before we
will need to throw another front end in there.

 

As for Jesse's question regarding what components we removed, going from
memory, the main things we did on the front end

==>     removed "quick ticket" link on "Home" page

==>     adding some extra caching to "quick search" box.

==>     removed information about requestor from ticket view page

==>     split off search formatting (eg, column selection) onto a
separate page

 

Not all these changes were speed related, and those that are could well
be redundant against 3.4 (we are running 3.2.2).

 

Regards,
Matt.

 

________________________________

From: rt-users-bounces at lists.bestpractical.com
[mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Yoav
Daniely
Sent: Sunday, February 27, 2005 5:11 PM
To: rt-users at lists.fsck.com
Subject: RE: [rt-users] Can RT scale up?

 

Matthew ,

 

Can you please elaborate concerning the hardware used ?

 

Regards,

 

        Yoav

 

________________________________

From: Matthew Watson [mailto:matthew.watson at staff.netspace.net.au] 
Sent: Friday, February 25, 2005 2:17 AM
To: Yoav Daniely; rt-users at lists.fsck.com
Subject: RE: [rt-users] Can RT scale up?

Hi,

 

 We currently have about 1.3 million tickets, and after a lot of
database tweaking and quite a bit of hardware we now have RT running
very reasonably. 

 

So, yes it can scale, however some of the design choices don't seem to
handle it that well, so you will most likely have to do a bit of work on
the indexes and possible the UI (we ripped out a number of slower
components) to make it an acceptable speed.

 

Regards,
Matt.

 

________________________________

From: rt-users-bounces at lists.bestpractical.com
[mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Yoav
Daniely
Sent: Thursday, February 24, 2005 11:52 PM
To: rt-users at lists.fsck.com
Subject: [rt-users] Can RT scale up?

 

Greetings,

 

I have a need to deploy RT to contain 250,000 tickets per year (and
import 3 years backwards from an old system).

Tickets will include at least 10 custom fields of extended information.

Anyone has any exprience/insights on this size of deployment? Any known
application design bottlenecks that may appear at high volumes such as
this?

 

Best Regards,

 

        Yoav Daniely

        Qball Technologies.

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. Please notify the sender immediately by email if you have
received this email by mistake and delete this email from your system.
Please note that any views or opinions presented in this email are
solely those of the author and do not necessarily represent those of the
organisation. Finally, the recipient should check this email and any
attachments for the presence of viruses. The organisation accepts no
liability for any damage caused by any virus transmitted by this email.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20050228/669305c6/attachment.htm>