I think i understood, so the autoextend option will grow the file as it came
data for it, so if i'll have in the future a database with 30GB or even
100GB (we never know) of data i don't need to worry 'cause it'll extend,
right?
Jorge
----- Original Message -----
From: "Andy Blackshaw" <[EMAIL PROTECTED]>
To: "DBMail mailinglist" <dbmail@dbmail.org>
Sent: Monday, April 03, 2006 1:01 PM
Subject: Re: [Dbmail] (no subject)
As it stands the config would create 2 ibdata files at startup of ~
1GB, 3GB, and 1GB, the last of these will grow automatically to 4GB
before you finally run out of space in innodb. As I said this config
evolved, I did not anticipate needing this much space, and haveing
filled the first 2 extents did not want to dump and restore so kept
them the same size and added a third. Normally, if practical I set the
first extent large enough to cope with expected requirement for say 2
years, but then add a 2nd extent at about 1/4th size but with
autoextend to cater for the almost inevitable unexpected demand. In
this case something like
ibdata1:4000M;ibdata2:1000M:autoextend:max:4000M
but whilst this policy has so far generally worked for me - this was
the first one I got the initial sizeing seriously wrong - I don't claim
any expertese, and as always ymmv.
It's not critical, if your estimate is too low you can add another
extent, the thing is to keep an eye on freespace within innodb so you
never reach the limit.
Autoextend grows the existing file, it does not split it, at least not
in the sense that you see multiple files, though the os may fragment
the growing file which is a reason not to make the primary extent(s)
too small
Andy
Andy or any other person that can answer me,
About this configuration for innodb that you gave me, what will happen
when
the database size passes the 1/3/4GB of data? the files will autosplit?
Is the "autoextend" option to make the files split by themselfs?
Jorge
>
> innodb_data_home_dir = /var/lib/mysql/
> innodb_data_file_path =
> ibdata1:1000M;ibdata2:3000M;ibdata3:1000M:autoextend:max:4000M
> innodb_log_group_home_dir = /var/lib/mysql/
> innodb_log_arch_dir = /var/lib/mysql/
> # You can set .._buffer_pool_size up to 50 - 80 %
> # of RAM but beware of setting memory usage too high
> set-variable = innodb_buffer_pool_size=192M
> set-variable = innodb_additional_mem_pool_size=20M
> # Set .._log_file_size to 25 % of buffer pool size
> set-variable = innodb_log_file_size=33554432
> set-variable = innodb_log_buffer_size=8M
> innodb_flush_log_at_trx_commit=1
> set-variable = innodb_lock_wait_timeout=50
_______________________________________________
Dbmail mailing list
Dbmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail
