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/
