[rt-users] speeding up rt-shredder

[ronald higgins]

Hi Garry,

The RT DB is currently 215GB in size, 1.5 Million Tickets (Attachments
table has 7 million entries).
Yes, this badboy is what I inherited with the new job. I've already
built another MySQL DB with the tables partitioned intended for
eventual cut over
but the last few days have seen the current prod db taking a hit
performance wise which is when i really started digging through the
tickets looking for a stop gap until we can cut over, and i'm sure
cutting the Tickets down by 700 000 will make a difference.

By all means, send it :) All tools of the trade are always gladly received :)


On Tue, Jul 27, 2010 at 9:20 PM, G.Booth <G.Booth at lboro.ac.uk> wrote:
> On Tue, 27 Jul 2010 20:33:03 +0200
>  ronald higgins <ronald.higgins at gmail.com> wrote:
>>
>> Thanks for the script Garry :)
>>
>> Unfortunately it's pretty much the same, every delete taking about 40
>> seconds, so it doesnt look like adding the SQL logging in is adding
>> any overhead :( pitty.
>
> OK, so that rules out overhead on the shredder. How big is your database and
> how many tickets are in your system? Im happy to benchmark what the script
> does on my RT compared to yours and see where we go.
> I can send you my pride and joy, which removes users that send spam, this
> combined with removing tickets should shrink your DB and may make life
> easier - hopefully you'll have a slow, one off, hit and then a manageable
> shred!
> You might also want to look at dealing with v large attachments.
>
> Off on hols now. Back 11th Aug - drop me a line if you dont get anywhere
> g.booth at lboro.ac.uk.
>
> Ditto the above, Max
>
> regards
> Garry
>