Re: Strange problem: Increasing Memory / HEAP Table

2006-03-13 Thread sheeri kritzer
What does SHOW CREATE TABLE give you?

-Sheeri

On 3/11/06, Holger Sunke [EMAIL PROTECTED] wrote:
 Hallo,

 is there a way of maintaining Memory tables or rebuilding indexes?

 I have a big memory table with about 300k rows, 12 Attributes, 7 
 BTREE-Indexes and a PRIMARY KEY (Hash index).

 Now i'm doing many many Updates (and a  little number of inserts) on this 
 table that also do effect indexed attributes.
 (With many updates I mean about 2000 per second...thats why I have chosen 
 Memory storage engine)

 The strange thing is that my table grows above linear to the happening 
 inserts, so average row size (=total memory used by table divided by number 
 of rows) increases too.

 When I now copy this table to another database or another table name by 
 CREATE TABLE new ... and then INSERT INTO new SELECT * FROM old
 memory used by new table can be about 50% (depends on number of actions done 
 on the old table before) of memory used by old table although Structure and 
 Data are equal.

 Could that be a bug? Table size especially of Memory tables should not 
 increase by updates i think...

 greets!

 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Strange problem: Increasing Memory / HEAP Table

2006-03-11 Thread Holger Sunke
Hallo,

is there a way of maintaining Memory tables or rebuilding indexes?

I have a big memory table with about 300k rows, 12 Attributes, 7 
BTREE-Indexes and a PRIMARY KEY (Hash index).

Now i'm doing many many Updates (and a  little number of inserts) on this table 
that also do effect indexed attributes.
(With many updates I mean about 2000 per second...thats why I have chosen 
Memory storage engine)

The strange thing is that my table grows above linear to the happening inserts, 
so average row size (=total memory used by table divided by number of rows) 
increases too.

When I now copy this table to another database or another table name by CREATE 
TABLE new ... and then INSERT INTO new SELECT * FROM old
memory used by new table can be about 50% (depends on number of actions done on 
the old table before) of memory used by old table although Structure and Data 
are equal.

Could that be a bug? Table size especially of Memory tables should not increase 
by updates i think...

greets!

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]