As Ananda mentioned, key_buffer is used for myisam. However I don't
think that's the reason. :-) Maybe mysql5.0 is the reason, or any
other system limitation?
On 7/25/08, Dominik Klein <[EMAIL PROTECTED]> wrote:
> Unfortunately, right now I can't.
>
> Someone mentioned getting rid of myisam config
Unfortunately, right now I can't.
Someone mentioned getting rid of myisam configuration values might help.
Which ones would that be?
Regards
Dominik
Xuekun Hu wrote:
I can alloc 14GB to innodb_buffer_pool_size, even 15GB on my 16GB
system. However I used mysql6.0, not mysql5.0. Maybe you can
I can alloc 14GB to innodb_buffer_pool_size, even 15GB on my 16GB
system. However I used mysql6.0, not mysql5.0. Maybe you can try newer
mysql version.
Thx, Xuekun
On 7/24/08, Ananda Kumar <[EMAIL PROTECTED]> wrote:
> Hi,
> U can use max of 80% of your Memory to Mysql, as OS needs the remaning.
>
Hi,
U can use max of 80% of your Memory to Mysql, as OS needs the remaning.
Also you can exclude Myisam parameter like key_buffer, as this i only
INNODB.
On 7/24/08, Dominik Klein <[EMAIL PROTECTED]> wrote:
>
> Hi
>
> I installed a 64bit Linux and compiled and installed 5.0.51b. This is to be
> a
Hi
I installed a 64bit Linux and compiled and installed 5.0.51b. This is to
be an innodb only system.
The machine has 16 GB of memory and I can see all of that with "free".
Except for mysql, there is nothing running on that system.
free -m
total used free shared
