> -----Original Message-----
> From: Marvin Wright [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 19, 2004 8:55 AM
> To: [EMAIL PROTECTED]
> Subject: InnoDB Load Problem
>
> Hi,
>
> Apologies in advance for the large post but I've tried to explain my
> problem
> as much as I can.
>
>
>
> I've read the InnoDB tuning page (
> http://dev.mysql.com/doc/mysql/en/InnoDB_tuning.html ), there are a few
> things I could try but I'd like to make sure that I'm on the right tracks.
>
> * Firstly I could put more queries into a single transaction.
That will help, increase your innodb_log_file_size and changed your
flush method to O_DIRECT - this avoids double writes. You can verify the
benefit of the change by looking at SHOW INNODB STATUS in the LOG IO
section.
Also, look at your buffer pool hit ratio. If its close to 100% then there is
no need to raise the allocation of the buffer_pool. Next, make sure you disk
layout is okay. Ensure that your not saturating on IO. Next make sure your
not doing queries like SELECT count(*) FROM <table> -- this is bad.
Finally look at which queries are slow. Make sure that your indexes are
proper.
One last note if your doing many many small quiries think about tweaking
your innodb_thread_conncurrency setting -- Ignore
innodb_thread_io_conncurrency unless you want to change code.
--
Dathan Vance Pattishall
Sr. Database Engineer / Sr. Programmer
Friendster Inc.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
