ktm at rice
May 11, 2008, 2:04 PM
Post #2 of 2
(106 views)
Permalink
|
Not to squash your hopes, but have you done any profiling to
determine where the slow points are located? You may want to
turn on exhausting logging and perform a ticket view and check
the performance of each query issued. If you have large attachments
the problem may be in the presentation of those attachments and
your partitioning will not really help. You could get a rough idea
by just checking the view times for a new ticket both with and without
an attachment. Good luck.
Cheers,
Ken
On Sun, May 11, 2008 at 11:25:41PM +0530, Yadavalli Aditya wrote:
> HI All,
>
> I am working on improving RT performance running on Oracle 10gR2 database.
> At present viewing ticket is taking almost 8-12 seconds. Everything on the
> database side looks OK. The database has got almost 1.5 Years of tickets
> (around 500,000 in number ) most of them are having attachements (on an
> average attachement size is 0.5 M) For improving the performance i am
> thinking of implementing partitioning on RT tables such as Tickets,
> Transactions, Attachments and so on... (Range-Hash partitioning ) i am
> quite not sure whether this will help me right afterwards. If any one has
> already implemented similar things... please share your experiences.
>
> Thanks,
> Aditya.
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Community help: http://wiki.bestpractical.com
> Commercial support: sales[at]bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: sales[at]bestpractical.com
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
|
