Hi,
Data migration made last night.
Use of a new MySQL instance has been quite useful to operate, the outage
was about 7 minutes.
ibdata1 is now using 58 MiB of disk space ! each table having a proper
.ibd file and full data directory from 13GiB to 3.2GiB ...
Server load divided by 3 ~ 4 ;).
I
Hi Shawn, and thanks for this concise anwser ;) .
Le 22/03/2014 05:35, shawn l.green a écrit :
>
> The system is operating exactly as designed. The ibdata* file(s) contain
> more than just your data and indexes. This is the common tablespace and
> it contains all the metadata necessary to identify
tabases
to recreate them ... ) the ibdata file , which is taking over 9GiB on
filesystem.
We have to separate data from databases in two cases , whilst it is
running , after setting innodb_file_per_table in MySQL configuration ,
and restarting service.
Creating First database, containing at oldest 6
over 9GiB on
filesystem.
We have to separate data from databases in two cases , whilst it is
running , after setting innodb_file_per_table in MySQL configuration ,
and restarting service.
Creating First database, containing at oldest 6 months of data.
Second database, considered "archive&q
Even more stuff inline there
>
> Actually, the gas tank is a good analogy.
>
> There is limited volume in a vehicle which must contain the tank. In this
> analogy, the vehicle must have space for not just fuel but passengers, cargo,
> engine, transmission, etc. The fact that the tank may
Hello all,
On 11/30/2011 16:46, Reindl Harald wrote:
Am 30.11.2011 19:13, schrieb Karen Abgarian:
Hi inline there.
On 30.11.2011, at 0:16, Reindl Harald wrote:
Most people do not expect a gas tank to shrink once the
gas is consumed...right?
WHO THE FUCK is comparing computers with
Am 30.11.2011 19:13, schrieb Karen Abgarian:
> Hi inline there.
>
> On 30.11.2011, at 0:16, Reindl Harald wrote:
>
>>
>>> Most people do not expect a gas tank to shrink once the
>>> gas is consumed...right?
>>
>> WHO THE FUCK is comparing computers with a gas tank?
> Well, I do. I even
Hi inline there.
On 30.11.2011, at 0:16, Reindl Harald wrote:
>
>> Most people do not expect a gas tank to shrink once the
>> gas is consumed...right?
>
> WHO THE FUCK is comparing computers with a gas tank?
Well, I do. I even managed to do it without using foul language.
Forgot to
Let's leave it at that, please.
- Original Message -
> From: "Reindl Harald"
> To: mysql@lists.mysql.com
> Sent: Wednesday, 30 November, 2011 9:16:51 AM
> Subject: [MySQL] innodb_file_per_table / apple workers and logic
>
> the defaults should not n
> [JS] I strongly suspect that MySQL, like any other random access, variable
> record length scheme, would find it easier to manage the internal layout of
> separate files. The rows would tend more to be of similar sizes, leading to
> less obnoxious fragmentation, and the files themselves would be
A significant gain you have with innodb_file_per_table is that of shrinking the
tablespaces.
You can do that with "OPTIMIZE TABLE ;"
You ibdata1 file should only contain metadata and some transaction logging info.
If your ibdata1 is gigantic, you have to do the following to shrink i
>-Original Message-
>From: Sebastien Moretti [mailto:sebastien.more...@unil.ch]
>Sent: Thursday, May 28, 2009 2:38 AM
>To: Baron Schwartz; mysql@lists.mysql.com
>Subject: Re: innodb_file_per_table cost
>
>> Hi Sebastian,
>>
>> It depends. In g
of
innodb index files, their sizes, ...
Hi,
Does the use of "innodb_file_per_table" option imply a performance cost ?
Compared to default: all InnoDB indexes are in ibdataX file(s).
Thanks
--
Sébastien Moretti
--
MySQL General Mailing List
For list archives: http://lists.mysql.co
s the use of "innodb_file_per_table" option imply a performance cost ?
> Compared to default: all InnoDB indexes are in ibdataX file(s).
>
> Thanks
>
> --
> Sébastien Moretti
--
Baron Schwartz, Director of Consulting, Percona Inc.
Our Blog: http://www.mysqlpe
Hi,
Does the use of "innodb_file_per_table" option imply a performance cost ?
Compared to default: all InnoDB indexes are in ibdataX file(s).
Thanks
--
Sébastien Moretti
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists
Hi everybody,
Does different table space with multiple databases is good for production
server. Is there any testing has been done. What is the impact on the other
things like speed.
Thanks,
--
Krishna Chandra Prajapati
MySQL DBA,
Ed Ventures e-Learning Pvt.Ltd.
1-8-303/48/15
Sindhi Colony
P.G.Ro
PROTECTED]> wrote:
> in /etc/my.cnf I set innodb_file_per_table in order to avoid a
> centralized set of ibdata* files,
> but that file (8 MB) is still present and continually updated.
> What can I do to make it vanish for good?
As it is stated in the documentation, you can'
In news:[EMAIL PROTECTED],
Nico Sabbi <[EMAIL PROTECTED]> wrote:
> in /etc/my.cnf I set innodb_file_per_table in order to avoid a
> centralized set of ibdata* files,
> but that file (8 MB) is still present and continually updated.
> What can I do to make it vanish for good?
Hi,
in /etc/my.cnf I set innodb_file_per_table in order to avoid a
centralized set of ibdata* files,
but that file (8 MB) is still present and continually updated.
What can I do to make it vanish for good? I'd like to have only
per-table ibd files.
The version of Mysql that I'
, some "table name.ibd" files are created when the
"innodb_file_per_table" parameter is specified.
I want to know How the MySQL server determines the initial size of "table
name .ibd" files and the extended size of them.
Please tell me about this .
With regards
--
Hello.
In InnoDB tables , some "table name.ibd" files are created when the
"innodb_file_per_table" parameter is specified.
I want to know How the MySQL server determines the initial size of "table
name .ibd" files and the extended size of them.
Please tell
Hello.
> Is there a specific innodb list?
There is an InnoDB forum:
http://forums.mysql.com/list.php?22
> disablign the keys. I think I tried that, but with a table with 7 mil
>rows, that takes longer than the load data :-\
Have you increased the myisam_sort_buffer_size variable to
George,
- Original Message -
From: ""George Law"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Sunday, January 08, 2006 10:10 PM
Subject: allocate space for innodb innodb_file_per_table
Hi All,
I am running mysql 5.0.18 with a innodb t
Hi All,
I am running mysql 5.0.18 with a innodb table of 9 GB (plus several others)
on suse linux 9.3 with 4 GB ram.
when doing a show table status command, this table shows Data_Free:0
I assume this is because it is the "file per table" setting, where the
tables fall outside of the main ibd
t: 26 July 2005 16:24
To: Marvin Wright; mysql@lists.mysql.com
Subject: Re: Correct way to use innodb_file_per_table?
On Jul 26, 2005, at 3:56 AM, Marvin Wright wrote:
>
> Regarding the file size issue, we are on a 32-bit system running
> redhat AS3, we already have idb files in excess of
On Jul 26, 2005, at 3:56 AM, Marvin Wright wrote:
Regarding the file size issue, we are on a 32-bit system running
redhat AS3,
we already have idb files in excess of 21Gb, I'm not sure what the
limit is
though if any ?
No, typically a 32 bit file system would have limits like 2G or 4G...
ubject: Re: Correct way to use innodb_file_per_table?
On Jul 25, 2005, at 5:33 AM, Marvin Wright wrote:
> Hi,
>
> Thanks for your reply.
>
> I've only just moved all tables to there own table space so that I can
> put certain databases on different disks.
> Right now my
than we would need if everything is
innodb_file_per_table... but as my old file space was made with 2000M
files I just kept ibdata01 and commented out the rest of the line
certainly haven't any issues with the 2Gbyte shared table space, I
would think 10G would be overkill (I think m
CTED]
Sent: 25 July 2005 12:53
To: Marvin Wright
Cc: mysql@lists.mysql.com
Subject: Re: Correct way to use innodb_file_per_table?
On Jul 25, 2005, at 5:47 AM, Marvin Wright wrote:
> You recommend to dump tables before changing then re-import them back.
> But if all databases are in t
On Jul 25, 2005, at 5:47 AM, Marvin Wright wrote:
You recommend to dump tables before changing then re-import them
back. But
if all databases are in there own tablespace I should need to do
this dump
should I ?
Unfortunately I think that's your only option to create a new table
space.
Hi,
Can anybody help with this ?
Regards,
Marvin
-Original Message-
From: Marvin Wright
Sent: 22 July 2005 10:46
To: Heikki Tuuri; mysql@lists.mysql.com
Subject: RE: Correct way to use innodb_file_per_table?
Hi Heikki,
I've followed your instructions here and its all worked
Hi,
I've just converted my databases so they are using per_table
tablespaces.
When I do a show table status in that database the Comment line
still shows
the amount free, but I assume this doesn't mean anything now ?? It
doesn't
make sense ?
As innodb_file_per_table m
way to use innodb_file_per_table?
Mike,
- Alkuperäinen viesti -
Lähettäjä: "Mike Debnam" <[EMAIL PROTECTED]>
Vastaanottaja:
Kopio: <[EMAIL PROTECTED]>
Lähetetty: Friday, March 04, 2005 2:49 PM
Aihe: Re: Correct way to use innodb_file_per_table?
> Heikki,
>
>> the
Hi,
I've just converted my databases so they are using per_table tablespaces.
When I do a show table status in that database the Comment line still shows
the amount free, but I assume this doesn't mean anything now ?? It doesn't
make sense ?
*** 1. row ***
Mike,
- Alkuperäinen viesti -
Lähettäjä: "Mike Debnam" <[EMAIL PROTECTED]>
Vastaanottaja:
Kopio: <[EMAIL PROTECTED]>
Lähetetty: Friday, March 04, 2005 2:49 PM
Aihe: Re: Correct way to use innodb_file_per_table?
Heikki,
the best way would be to symlink whole data
drive 2.
>
Hmm, ok. I have just one decent size database though. I want to split
the tables in that database between disks. I haven't turned on
innodb_file_per_table yet I'm trying to plan it out first, so I don't
know the file layout yet. If my data directory is /var/db/mysql a
Mike,
- Original Message -
From: "Mike Debnam" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Friday, March 04, 2005 6:15 AM
Subject: Correct way to use innodb_file_per_table?
I've added a second drive to my database machine and want to split my
da
rect way to use
innodb_file_per_table? If my datadir is /var/db/mysql , should I let
MySQL create all the tables in /var/db/mysql then move the files and
create symlinks in /var/db/mysql?
I see a note in the InnoDB docs that says you can't move the *.ibd
files around, what does that refer to?
System is Fre
arsten" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm using InnoDB with the "innodb_file_per_table" option on.
> But now my .MYD-file has reached the maximum filesize of my filesystem
> and i have to add a new tablespace.
>
> Can someone tell me h
Carsten,
- Original Message -
From: ""Grumm, Carsten"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, January 26, 2005 4:22 PM
Subject: Out of tablespace when using innodb_file_per_table
Hello,
I'm using InnoDB with the "i
Hello,
I'm using InnoDB with the "innodb_file_per_table" option on.
But now my .MYD-file has reached the maximum filesize of my filesystem
and i have to add a new tablespace.
Can someone tell me how?
Thanks in advance for your help
Carsten
--
MySQL General Mailing List
For list
Hi!
If you have put:
innodb_file_per_table
in your my.cnf or my.ini in Windows, and try to run MySQL-4.1.9, the mysqld
server exits and prints:
"
050117 3:07:59 InnoDB: Operating system error number 87 in a file
operation.
"
to the .err log.
You can work around the bug in 4.1.9
Hi!
http://bugs.mysql.com/bug.php?id=7496
A critical bug found: if one uses the 4.1 my.cnf option
innodb_file_per_table
to create tables, and some of the secondary index records are inserted to
the InnoDB 'insert buffer', then after a normal mysqld shutdown InnoDB loses
all those secon
;
<[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, November 11, 2004 9:59 PM
Subject: Re: InnoDB data files keep growing with innodb_file_per_table
John,
please zip ibdata1, which is 'only' 100 MB, and upload it when you
have shut
down mysqld.
I have been s
ww.innodb.com/order.php
Order MySQL technical support from https://order.mysql.com/
- Original Message -
From: ""Heikki Tuuri"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, November 11, 2004 9:59 PM
Subject: Re: InnoDB data files keep grow
<[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, November 11, 2004 8:17 PM
Subject: Re: InnoDB data files keep growing with innodb_file_per_table
Heikki,
Heikki Tuuri wrote:
hmm... could it be that segments 0 1, 0 2, 0 3, etc. were printed close
to the end of the output? The print routi
Sasha,
- Original Message -
From: "Sasha Pachev" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, November 11, 2004 8:05 PM
Subject: Re: InnoDB data files keep growing with innodb_file_per_table
Heikki Tuuri wrote:
Ivan,
hmm... could it be that s
Heikki,
Heikki Tuuri wrote:
hmm... could it be that segments 0 1, 0 2, 0 3, etc. were printed close
to the end of the output? The print routine first prints inode pages
that are completely used, and after that other inode pages. Since the
tablespace validation said the tablespace is ok, I guess
Heikki Tuuri wrote:
Ivan,
hmm... could it be that segments 0 1, 0 2, 0 3, etc. were printed close
to the end of the output? The print routine first prints inode pages
that are completely used, and after that other inode pages. Since the
tablespace validation said the tablespace is ok, I guess th
Heikki,
Heikki Tuuri wrote:
InnoDB is clearly leaking 'segments' in the system tablespace. They are
probably undo logs. For some reason, a trx commit or purge fails to free
them.
SEGMENT id 0 75994 space 0; page 82136; res 2720 used 2680; full ext 41
fragm pages 32; free extents 0; not full exte
InnoDB data files keep growing with innodb_file_per_table
Ivan,
there is something very strange in your tablespace monitor output:
04 5:35:51 INNODB TABLESPACE MONITOR OUTPUT
FILE SPACE INFO: id 0
s
1, 2004 10:16 AM
Subject: Re: InnoDB data files keep growing with innodb_file_per_table
Ivan,
- Original Message -
From: ""John B. Ivski"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, November 11, 2004 4:55 AM
Subject: Re: InnoDB data files
Ivan,
- Original Message -
From: ""John B. Ivski"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, November 11, 2004 4:55 AM
Subject: Re: InnoDB data files keep growing with innodb_file_per_table
Heikki,
the output shows that there ar
Heikki,
I can think of another explanation. Are you sure that all your tables
really are in .ibd files? Maybe some older tables are actually in the
ibdata files?
Yes I'm sure they're all in .ibd files (and I've just checked just in case
- they are indeed).
Please use the innodb_tablespace_monito
alues (...),...,(...)
on duplicate key update data1=values(data1),dataN=values(dataN)
so primary keys don't get updated...
Please shut down mysqld, remove
innodb_file_per_table
from my.cnf, and restart mysqld. Then do
CREATE TABLE test.t(a INT) TYPE=InnoDB;
Then do
SHOW TABLE STATUS FROM test;
What does i
uot;Heikki Tuuri"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, November 11, 2004 1:55 AM
Subject: Re: InnoDB data files keep growing with innodb_file_per_table
John,
the output shows that there are no dangling transactions, and purge is not
lagging behind.
John,
the output shows that there are no dangling transactions, and purge is not
lagging behind.
If you update a secondary index column, that requires purge to clean up the
index.
Please shut down mysqld, remove
innodb_file_per_table
from my.cnf, and restart mysqld. Then do
CREATE TABLE test.t
d 593305, updated 1606540, deleted 0, read 453171610
1.79 inserts/s, 4.00 updates/s, 0.00 deletes/s, 571.89 reads/s
END OF INNODB MONITOR OUTPUT
- Original Message - From: ""John B. Ivski"" <[EMAIL PROTECTED]>
Newsgroups: maili
ct: InnoDB data files keep growing with innodb_file_per_table
Hello,
I have a DB of about 100 tables, and MySQL is configured to keep them in
separate files. Total size
of the files is ~2GB. Most of the tables are of similar format and consist
of many short
fixed-length rows (~50 bytes/
_size=128M
innodb_log_file_size=64M
innodb_thread_concurrency=8
innodb_file_per_table
innodb_open_files=2048
Good luck,
John
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Hi!
MySQL/InnoDB-4.1.2 is totally broken and useless if one has specified
innodb_file_per_table in my.cnf on Unix!
In crash recovery, InnoDB scans the database directories under the datadir,
and opens files in in the read-only mode. But the exclusive file lock that
InnoDB uses on the files fails
61 matches
Mail list logo
