Home > Archive > MySQL ODBC Connector > April 2005 > ibdata1 grows beyound borders..









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author ibdata1 grows beyound borders..
Eric Persson

2005-04-26, 3:23 am

Hi,

I've been running a innodbdatabase for a while, and it works nice,
however, I've noticed that it have grown beyound the specifications in
the my.cnf file. I did define autoextend so its not very strange,
however, I was wondering, how far can it grow, and is it a bad idea to
just let it grow?

the my.cnf looks like:
[mysqld]
datadir=/usr/local/mysql/data/
socket=/tmp/mysql.sock
set-variable = max_connections=200
set-variable = thread_cache_size=20

innodb_data_home_dir
=
innodb_data_file_pat
h = /usr/local/mysql/data/ ibdata1:2000M:autoex
tend
set-variable = innodb_buffer_pool_s
ize=200M
set-variable = innodb_additional_me
m_pool_size=20M
innodb_log_group_hom
e_dir = /usr/local/mysql/data/innodb/
innodb_log_arch_dir = /usr/local/mysql/data/innodb/
set-variable = innodb_log_files_in_
group=2
set-variable = innodb_log_file_size
=50M
set-variable = innodb_log_buffer_si
ze=8M
innodb_flush_log_at_
trx_commit=0
set-variable = innodb_lock_wait_tim
eout=50
set-variable = long_query_time=15
#log-long-format
log-slow-queries = /var/log/mysqld.slow.log


[mysql.server]
user=mysql
basedir=/usr/local/mysql


[safe_mysqld]
err-log=/var/log/mysqld.log
pid-file=/usr/local/mysql/data/db.bcmanga.se.pid

The ibdata1 is now around 7gb and it keeps growing..

How big can it be? Is it innodb dependent or os dependent? I'm currently
running Fedora Core release 3 (Heidelberg) on a dual xeon 3ghz with 3gb
ram.

Can I just define some more ibdata files and it will re-arrange the data
by itself, or do I need to export and them import it? Or whats the best
practice here?

Thanks in advance,
Eric


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql? unsub...sie.nctu.edu.tw

Gleb Paharenko

2005-04-26, 7:23 am

Hello.

Searching in the archives says you could get worse performance, because
of extending during transactions:

http://lists.mysql.com/mysql/180037
http://lists.mysql.com/mysql/170946


Eric Persson <eric@persson.tm> wrote:
> Hi,
>
> I've been running a innodbdatabase for a while, and it works nice,
> however, I've noticed that it have grown beyound the specifications in
> the my.cnf file. I did define autoextend so its not very strange,
> however, I was wondering, how far can it grow, and is it a bad idea to
> just let it grow?
>
> the my.cnf looks like:
> [mysqld]
> datadir=/usr/local/mysql/data/
> socket=/tmp/mysql.sock
> set-variable = max_connections=200
> set-variable = thread_cache_size=20

> innodb_data_home_dir
=
> innodb_data_file_pat
h = /usr/local/mysql/data/ ibdata1:2000M:autoex
tend
> set-variable = innodb_buffer_pool_s
ize=200M
> set-variable = innodb_additional_me
m_pool_size=20M
> innodb_log_group_hom
e_dir = /usr/local/mysql/data/innodb/
> innodb_log_arch_dir = /usr/local/mysql/data/innodb/
> set-variable = innodb_log_files_in_
group=2
> set-variable = innodb_log_file_size
=50M
> set-variable = innodb_log_buffer_si
ze=8M
> innodb_flush_log_at_
trx_commit=0
> set-variable = innodb_lock_wait_tim
eout=50
> set-variable = long_query_time=15
> #log-long-format
> log-slow-queries = /var/log/mysqld.slow.log
>
>
> [mysql.server]
> user=mysql
> basedir=/usr/local/mysql
>
>
> [safe_mysqld]
> err-log=/var/log/mysqld.log
> pid-file=/usr/local/mysql/data/db.bcmanga.se.pid
>
> The ibdata1 is now around 7gb and it keeps growing..
>
> How big can it be? Is it innodb dependent or os dependent? I'm currently
> running Fedora Core release 3 (Heidelberg) on a dual xeon 3ghz with 3gb
> ram.
>
> Can I just define some more ibdata files and it will re-arrange the data
> by itself, or do I need to export and them import it? Or whats the best
> practice here?
>
> Thanks in advance,
> Eric
>
>



--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Gleb Paharenko
/ /|_/ / // /\ \/ /_/ / /__ Gleb.Paharenko@ensita.net
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
<___/ www.mysql.com




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql? unsub...sie.nctu.edu.tw

Eric Persson

2005-04-26, 7:23 am

Gleb Paharenko wrote:

> Hello.
>
> Searching in the archives says you could get worse performance, because
> of extending during transactions:
>


Yes, read a few of those, but how about the fix for this, will the data
rearrange itself automatically when I specify more files?

//Eric


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql? unsub...sie.nctu.edu.tw

Gleb Paharenko

2005-04-26, 11:24 am

Hello.

I don't think so. As I've understood InnoDB doesn't do it. See:

http://dev.mysql.com/doc/mysql/en/i...file-space.html



Eric Persson <eric@persson.tm> wrote:
> Gleb Paharenko wrote:
>
>
> Yes, read a few of those, but how about the fix for this, will the data
> rearrange itself automatically when I specify more files?
>
> //Eric
>
>



--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Gleb Paharenko
/ /|_/ / // /\ \/ /_/ / /__ Gleb.Paharenko@ensita.net
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
<___/ www.mysql.com




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql? unsub...sie.nctu.edu.tw

Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com