Results 1 to 6 of 6
Thread: MYSQL and tmp_table_size problem
-
05-11-2007, 04:56 PM #1Web Hosting Evangelist
- 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 ?
-
05-11-2007, 05:06 PM #2Web Hosting Master
- Join Date
- Jan 2005
- Posts
- 2,203
Same here.
-
05-11-2007, 05:30 PM #3Web Hosting Master
- Join Date
- Jun 2004
- Location
- Oregon
- Posts
- 1,315
seems RAM is not enough.
-
05-11-2007, 05:37 PM #4Web Hosting Evangelist
- 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
-
05-14-2007, 05:46 PM #5Web Hosting Evangelist
- Join Date
- Jan 2005
- Posts
- 483
Really nobody knows ?
-
05-14-2007, 06:02 PM #6Predatory Poster
- 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.
If you want faster results pay someone.