Sorry I failed to specify ghatna is only applicable when the database is quiet large.
From: "Reindl Harald" <h.reindl@stripped>
Sent: 16-05-2013 14:43
To: "mysql@stripped" <mysql@stripped>
Subject: Re: Innodb innodb_buffer_pool_size?
Am 16.05.2013 11:01, schrieb Vikas Shukla:
> The best value for innodb buffer pool size is considered to be 60 to 70 percent of
> So in your case, this must be around 4 gb.
> That would work better.
hwo would a innodb_buffer_pool larger than the whole database
make anything better? the best value is as large as the
expected dataset, more is wasting system ressources
> -----Original Message-----
> From: "Claudio Nanni" <claudio.nanni@stripped>
> Sent: 16-05-2013 14:12
> To: "Rafał Radecki" <radecki.rafal@stripped>
> Cc: "mysql@stripped" <mysql@stripped>
> Subject: Re: Innodb innodb_buffer_pool_size?
> Hi Rafal,
>> I am trying to set the best value for innodb_buffer_pool_size. My system
> has 6GB of ram.
>> My question: how to tell if my innodb_buffer_pool_size is ok?
> If this is a MySQL dedicated server,
> In your case I would set it to 2GB-3GB.
> You will have the whole data in RAM now and for some time.
>> Does Buffer pool hit rate 1000 / 1000 mean that I can lower it?
> No. It means it is doing fine. And if you don't need RAM for anything else
> why lower it?
>> Does Free buffers 0 mean that I should make it larger?
> No. InnoDB will always try to allocate each block in the buffer pool.
>> Eventually what else to check?
> (a) mysql> SELECT engine,sum(data_length)/1024/1024 as
> DATA_MB,sum(INDEX_LENGTH)/1024/1024 as INDEX_MB FROM
> information_schema.tables GROUP BY engine;
> To check the real size of the dataset.
> (b) Note: mysql-server-5.0.58 you should upgrade to latest 5.0.96
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / CISO / Software-Development
p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
icq: 154546673, http://www.thelounge.net/