Few things you can do to help already running optimize table processes :
1. Turn off competing processes.
2. Make sure there is no read caching on in your raid controller.
3. Taking the machine OOR also helps.
For future optimize commands :
Is your deletion process based on some date ? If so have you considered
using Merge tables and MyISAM. If you do so, then purging becomes just
dropping a table an running an alter table on Merge which is very fast.
--
Thanks
Alex
http://alexlurthu.wordpress.com
On Mon, May 26, 2008 at 1:03 PM, Ananda Kumar <anandkl@stripped> wrote:
> Hi Sebastian,
> Now that table is already in production, so is there a way i can speed up
> the optimize table command.
>
> regards
> anandkl
>
>
> On 4/29/08, Sebastian Mendel <lists@stripped> wrote:
> >
> > Ananda Kumar schrieb:
> >
> >> Hi All,
> >> I am using mysql 5.0.41 on debain.
> >> I have 8 processor, 8 GB RAM.
> >> I have atable with 95 Million records, each day there will be about 1.5
> >> Million records deleted, and around 3.5 Million records added using
> "LOAD
> >> FILE" script.
> >>
> >> Since there would daily deletes happening, there would be lot of
> >> fragmention, so i used the
> >> analyze table <table_name>; command to defragment it, it took close
> to
> 12
> >> hrs. Is there any better and faster way to analyze or optimize the table
> >> to
> >> defragmentation.
> >>
> >
> > having a fixed row length will prevent tale fragmentation
> >
> > --
> > Sebastian
> >
> > --
> > MySQL General Mailing List
> > For list archives: http://lists.mysql.com/mysql
> > To unsubscribe: http://lists.mysql.com/mysql?unsub=1
> >
> >
>
