List:General Discussion« Previous MessageNext Message »
From:mos Date:June 25 2009 6:32am
Subject:Re: Indexing dynamics in MySQL Community Edition 5.1.34
View as plain text  
At 12:37 AM 6/25/2009, you wrote:
>Actually, my characterization of the current state is wrong.  It appears
>that one core is completely busy, I suppose MySQL does this indexing work
>in a single thread.  Is it reasonable for indexing to be CPU bound?
>
>
>my.cnf based on my-huge.cnf, expanding key_buffer to 8G,
>myisam_sort_buffer_size to 256M, and putting tmpdir on the fiber channel
>disk.

Mike,
     You mean "key_buffer_size" don't you and not "key_buffer"? If you are 
using MySQL 5.0 then the upper limit is 4gb but 5.1 allows for more than 4gb.
Also try increasing "sort_buffer_size".

Posting your "Show Status" will help people see where the bottle neck is.

Mike 

Thread
Indexing dynamics in MySQL Community Edition 5.1.34Mike Spreitzer25 Jun
  • Re: Indexing dynamics in MySQL Community Edition 5.1.34Mike Spreitzer25 Jun
    • Re: Indexing dynamics in MySQL Community Edition 5.1.34mos25 Jun
      • Re: Indexing dynamics in MySQL Community Edition 5.1.34Mike Spreitzer25 Jun
      • Re: Indexing dynamics in MySQL Community Edition 5.1.34Simon J Mudd27 Jun
    • RE: Indexing dynamics in MySQL Community Edition 5.1.34Jerry Schwartz25 Jun
Re: Indexing dynamics in MySQL Community Edition 5.1.34mos25 Jun
  • Re: Indexing dynamics in MySQL Community Edition 5.1.34Moon's Father26 Jun
    • RE: Indexing dynamics in MySQL Community Edition 5.1.34Jerry Schwartz26 Jun
      • RE: Indexing dynamics in MySQL Community Edition 5.1.34Jerry Schwartz26 Jun
  • Re: Indexing dynamics in MySQL Community Edition 5.1.34Mike Spreitzer27 Jun
    • Re: Indexing dynamics in MySQL Community Edition 5.1.34Mike Spreitzer27 Jun
      • Re: Indexing dynamics in MySQL Community Edition 5.1.34Todd Lyons27 Jun