Bug #11374 | SQL command OPTIMIZE TABLE memory leak | ||
---|---|---|---|
Submitted: | 16 Jun 2005 10:11 | Modified: | 23 Jun 2005 13:41 |
Reporter: | Julien VALIENTE | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 4.0.17 | OS: | Linux (RedHat 8.0) |
Assigned to: | CPU Architecture: | Any |
[16 Jun 2005 10:11]
Julien VALIENTE
[23 Jun 2005 13:41]
Aleksey Kishkin
Hi! run your program against mysql 4.0.24 and tested memory it ate: $> for i in `seq 1 20`;do ps -eo fname,sz |grep mysql|tail -n 1;sleep 1; done mysqld 14272 mysqld 14489 mysqld 14926 mysqld 14755 mysqld 14371 mysqld 14189 mysqld 14713 mysqld 14135 mysqld 14140 mysqld 15029 mysqld 14596 mysqld 14366 mysqld 14233 mysqld 15023 mysqld 14434 mysqld 14714 mysqld 14434 mysqld 14141 mysqld 14091 mysqld 14282 I dont see if mysql server grows. How did you estimated mysql server size in memory?
[23 Jun 2005 14:02]
Julien VALIENTE
I used the linux 'top' tool to estimate the mysql daemon memory usage.