5.5.4부터 들어간 설정값 - innodb_buffer_pool_instances

불당   
   조회 14852  

16G로 innodb_buffer_pool_size를 잡았을 때...

innodb_buffer_pool_instances = 8



This option takes effect only when you set the innodb_buffer_pool_size to a size of 1 gigabyte or more. The total size you specify is divided among all the buffer pools. For best efficiency, specify a combination ofinnodb_buffer_pool_instances and innodb_buffer_pool_size so that each buffer pool instance is at least 1 gigabyte.

I learned something amazing about MySQL. If you allocate a single monolithic InnoDB Buffer Pool that is bigger that Total Installed Divided By Number of Physical CPUs, your will incite the OS to regular intervals memory swapping due to a full InnoDB Buffer Pool. MySQL 5.5's option known asinnodb_buffer_pool_instances can be used to split up the buffer pool. Yesterday, I properly implemented this for the client I mentioned in my answer last year. I still have 162GB for the client's Buffer Pool. I have set the server's innodb_buffer_pool_instances option to 2 because each DB Server is dual hexacore. I was thinking of setting it to 12 but then a colleague showed me a blog from Jeremy Cole on MySQL and Swappiness. After reading it, I put it into practice immediately for my client. I ran this command
- opencode.co.kr -
불당 2013-02
어... 이 옵션쓰고 메모리 사용량이 팍~ 줄어들었네요. ㄷㄷㄷ...


제목Page 3/9
     
2016-05   37713   불당
2016-05   59254   불당
2018-06   19767   불당
2016-08   41024   불당
2016-07   54394   불당
2013-02   14853   불당
2013-02   8332   불당
2013-02   10449   불당
2013-02   6835   불당
2013-02   7453   불당
2013-01   7611   불당
2013-01   6674   불당
2013-01   8115   불당
2013-01   5855   불당
2013-01   7281   불당
2012-12   7484   불당
2012-12   8275   불당
2012-11   7319   불당
2012-11   6478   불당
2012-11   6445   불당
2012-11   9012   불당
2012-11   8438   불당
2012-10   10448   불당
2012-10   11229   불당
2012-10   7535   불당