[rt-users] MySQL Scaling for a large instance

[ktm at rice.edu]

Hi David,

Our instance is not large, but have you tried profiling the load on
the database to find out where your resource shortages are located?
This will help you target the changes needed to improve the performance
of the backend. As Ronald mentions, the first step would be to use
partitioning to allow the working set of the database to remain in
memory for current queries.

Cheers,
Ken

On Tue, Mar 13, 2012 at 07:12:28PM +0200, ronald higgins wrote:
> hi David.
> 
> Our instance of RT is around 3.5 million records and the mySQL db about
> 470GB in size. the biggest performance gain I've got was through
> partitioning and indexing, i'm very keen to see where this thread goes for
> "bigger" deployments as i'm also concerned about that breaking point.
> 
> regards
> 
> Ronald
> On 13 Mar 2012 19:03, "David Moreau Simard" <dmsimard at iweb.com> wrote:
> 
> > Hi,
> >
> > Our RT instance is rather large (> 5 million tickets) and I wondered if
> > any users have had to deal with a RT database this size and if so, how they
> > scaled their infrastructure as a result.
> >
> > Right now, the web portion is hosted on a cluster and really, this part
> > doesn't worry me at all.
> > I am really curious what are our options to get the best possible database
> > performance at this point.
> >
> > A thought we had was to split reads and writes since we have significantly
> > higher demand for read operations and they can be scaled/load-balanced with
> > relative ease.
> > Has anyone attempted to do this ? RT doesn't seem to be able to do this
> > out of the box.
> >
> > Do you otherwise have other recommendations ?
> >
> > Thanks !
> > --
> > *David Moreau Simard*
> > /IT Specialist/
> >
> >