[rt-users] speeding up rt-shredder

[Asif Iqbal]

On Tue, Jul 27, 2010 at 3:54 PM, G.Booth <G.Booth at lboro.ac.uk> wrote:
> On Tue, 27 Jul 2010 21:28:37 +0200
>  ronald higgins <ronald.higgins at gmail.com> wrote:
>>
>> 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
>> :)
>
> OMFG!
> Mine is 4GB, 150000 tickets, so it looks like you've got some big
> attachments!
>
> Think this will be painful!
> will send script with explanation when I get back.
> I'd seriously look at the attachments table as my RT is 10% of yours in
> tickets, but only 2% the size.
>
> Can you zap attachments above 1Gb?

would be nice if the attachments could be converted to link.
we have a ftp server in same network  that has lots of space.

Anyone has done anything like this?

If you reply please change the subject too.

>
>
> regards
> Garry
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
>



-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?