# MySQL settings for low-end server

**URL:** <https://forums.percona.com/t/mysql-settings-for-low-end-server/1248>\
**Category:** Other MySQL® Questions\
**Created:** [August 28, 2009, 12:53am UTC](https://forums.percona.com/t/mysql-settings-for-low-end-server/1248 "2009-08-28T00:53:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Keeper](https://avatars.discourse-cdn.com/v4/letter/k/278dde/32.png) [@Keeper](https://forums.percona.com/u/Keeper)\
**Post date:** [August 28, 2009, 12:53am UTC](https://forums.percona.com/t/mysql-settings-for-low-end-server/1248/1 "2009-08-28T00:53:27Z")

</div>

Hello,

Can I please get some assistance to determine best settings for a Debian linux server that is dual-core and has 2GB RAM? It is your typical all-around web server running Apache2 (mpm worker), PHP5 (fcgid), MySQL5, PureFTPd.

MySQL is serving around a dozen databases, both MyISAM and InnoDB tables. Biggest databases are 2GB, biggest tables 1.5GB.

I need to tune MySQL so that it doesn’t take all RAM even under heavy load but leaves plenty to Apache and other services running on the server. Before applying values below on live server, I’d like to hear expert opinions on them. )

| [B]Quote:[/B] |
| 

key\_buffer = 128M  
thread\_cache\_size = 64  
table\_cache = 1024  
thread\_concurrency = 4  
key\_buffer\_size = 256M  
thread\_cache = 4

query\_cache\_limit = 1M  
query\_cache\_size = 32M

innodb\_buffer\_pool\_size = 256M  
innodb\_additional\_mem\_pool\_size = 20M  
innodb\_log\_buffer\_size = 8M  
innodb\_log\_file\_size = 32M  
innodb\_flush\_log\_at\_trx\_commit = 2

 |

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![gmouse](https://avatars.discourse-cdn.com/v4/letter/g/b9e5f3/32.png) [@gmouse](https://forums.percona.com/u/gmouse)\
**Post date:** [August 28, 2009, 4:47am UTC](https://forums.percona.com/t/mysql-settings-for-low-end-server/1248/2 "2009-08-28T04:47:01Z")

</div>

key\_buffer is deprecated and replaced by key\_buffer\_size. You specify both. Just remove ‘key\_buffer = 128M’.

Aside from that it is hard to say anything without knowing more about your data, distribution among MyISAM/InnoDB, and about index sizes.
