5.5.4부터 들어간 설정값 - innodb_buffer_pool_instances

불당   
   조회 15340  

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
     
2015-05   101597   불당
2016-05   66676   불당
2015-10   86753   불당
2015-09   84873   불당
2018-06   27046   불당
2013-02   15341   불당
2013-02   8465   불당
2013-02   10638   불당
2013-02   7069   불당
2013-02   7614   불당
2013-01   7751   불당
2013-01   6836   불당
2013-01   8258   불당
2013-01   5983   불당
2013-01   7415   불당
2012-12   7606   불당
2012-12   8408   불당
2012-11   7449   불당
2012-11   6611   불당
2012-11   6596   불당
2012-11   9178   불당
2012-11   8601   불당
2012-10   10753   불당
2012-10   11367   불당
2012-10   7686   불당