Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an application that has few concurrent connections but does a lot of uncacheable fulltext searches sorting, limit with offset, etc. I have an xlarge instance with innodb buffer pool size @ 75% of available memory, tmp table size is set at 64M. temp table status shows lots of in memory and in disk temp table creation. client vars are:

sort_buffer_size 2M read_buffer_size 2M read_rnd_... 4M

I am thinking of bumping up the temp table size and other sort related vars by scaling down the innodb buffer pool. Does that even make sense? By the way we are not using provisioned iops either.

share|improve this question
Does your max_heap_table_size match your configured tmp_table_size? MySQL will use the lesser of the two. – Derek Downey Apr 18 '13 at 12:21
yes it is. thanks, Derek. – JShean Apr 18 '13 at 12:23

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.