Results 1 to 6 of 6
  1. #1
    Join Date
    Jan 2005
    Posts
    483

    * MYSQL and tmp_table_size problem

    Hello,

    I used tuning_primer script to tune up my mysql server.

    The problem is with tmp_table_size

    Its already set to 256M and tuning_primer still shows that 77% of tmp tables were created on HDD. Is there a way to optimalize SQL requests to make it lower ? or what should I do ?

  2. #2
    Join Date
    Jan 2005
    Posts
    2,203
    Same here.

  3. #3
    Join Date
    Jun 2004
    Location
    Oregon
    Posts
    1,315
    seems RAM is not enough.

  4. #4
    Join Date
    Jan 2005
    Posts
    483
    Code:
                total       used       free     shared    buffers     cached
    Mem:          2025       1951         74          0        158       1348
    -/+ buffers/cache:        444       1580
    Swap:         1027         12       1014
    Don't think so.

  5. #5
    Join Date
    Jan 2005
    Posts
    483
    Really nobody knows ?

  6. #6
    Join Date
    Jul 2003
    Location
    Goleta, CA
    Posts
    5,566
    http://dev.mysql.com/doc/refman/5.0/...variables.html

    tmp_table_size
    The maximum size of in-memory temporary tables. (The actual limit is determined as the smaller of max_heap_table_size and tmp_table_size.) If an in-memory temporary table exceeds the limit, MySQL automatically converts it to an on-disk MyISAM table. Increase the value of tmp_table_size (and max_heap_table_size if necessary) if you do many advanced GROUP BY queries and you have lots of memory.
    It could be exceeding the max_heap_table_size and converting to on disk tables.

    If you want faster results pay someone.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •