List:General Discussion« Previous MessageNext Message »
From:Ananda Kumar Date:September 25 2008 11:40am
Subject:Re: mysql big table select speed
View as plain text  
On the new machine its on a different partition than the database.

Also did u try to analyze the table and run the query


On 9/25/08, Carles Pina i Estany <carles@stripped> wrote:
>
>
> Hello,
>
> On Sep/25/2008, Ananda Kumar wrote:
> > is /tmpdir parameter on both machines using the default value
>
> Old machine: yes.
>
> New machine: I have tried two places (different partitions, same FS
> -ext3-, same hard disk). On the old machine it's in a different
> partition of the same hard disk than the database, same thing happends
> in the new server.
>
> Thanks,
>
> >
> > On 9/25/08, Carles Pina i Estany <carles@stripped> wrote:
> > >
> > >
> > > Hello,
> > >
> > > On Sep/25/2008, Ananda Kumar wrote:
> > > > does it have the same network speed as your old server.
> > >
> > > yes, it has. But I'm running the query from localhost :-) (socket
> > > connection). Even, the query only returns one number and I don't have
> > > any federated tables, etc.
> > >
> > > >
> > > > On 9/25/08, Carles Pina i Estany <carles@stripped> wrote:
> > > > >
> > > > >
> > > > > Hello,
> > > > >
> > > > > On Sep/24/2008, Phil wrote:
> > > > > > Just a wild guess but, did you perhaps change the filesystem
> to a
> > > > > > journalling filsystem when moving to the different server?
> > > > >
> > > > > mount reports the same (ext3)
> > > > >
> > > > > > I once accidently moved my database from an ext2 to an ext3
> partition
> > > and
> > > > > it
> > > > > > took me a while to figure out the degradation of queries..
> > > > >
> > > > > I have problems reading (selecting) and without any writing disk
> > > > > activity (I mean, no temporary tables, etc.). Journaling could
> affect
> > > > > writing but not reading, no?
> > > > >
> > > > > But I already thought about it :-) and tune2fs -l /dev/partition
> in
> > > both
> > > > > servers reports something different:
> > > > >
> > > > > New one:
> > > > > Filesystem features:      has_journal resize_inode dir_index
> filetype
> > > > > needs_recovery sparse_super large_file
> > > > >
> > > > > Old one:
> > > > > Filesystem features:      has_journal filetype needs_recovery
> > > > > sparse_super large_file
> > > > >
> > > > > I think that this "resize_inode" is not a problem. I don't know
> why
> > > > > appears "needs_recovery". Both filesystems are "Clean", etc.
> > > > >
> > > > > Thanks for your idea, do we have more ideas? :-) or anything
> else
> to
> > > > > check...
> > > > >
> > > > > --
> > > > > Carles Pina i Estany            GPG id: 0x17756391
> > > > >        http://pinux.info
> > > > >
> > > > > --
> > > > > MySQL General Mailing List
> > > > > For list archives: http://lists.mysql.com/mysql
> > > > > To unsubscribe:
> > > http://lists.mysql.com/mysql?unsub=1
> > > > >
> > > > >
> > > --
> > > Carles Pina i Estany            GPG id: 0x17756391
> > >        http://pinux.info
> > >
> --
> Carles Pina i Estany            GPG id: 0x17756391
>        http://pinux.info
>

Thread
mysql big table select speedCarles Pina i Estany25 Sep
  • Re: mysql big table select speedPhil25 Sep
    • Re: mysql big table select speedCarles Pina i Estany25 Sep
      • Re: mysql big table select speedAnanda Kumar25 Sep
        • Re: mysql big table select speedCarles Pina i Estany25 Sep
Re: mysql big table select speedAnanda Kumar25 Sep
  • Re: mysql big table select speedCarles Pina i Estany25 Sep
    • Re: mysql big table select speedAnanda Kumar25 Sep
      • Re: mysql big table select speedCarles Pina i Estany25 Sep