DB-Size-Savings are calculated wrong

Hey arcticblue,

Thanks for the compliments.

About the DB-Size:
I calculate the size when the clean-up process starts and I calculate the size again at the end of the process.

However, the database is dynamic: during the clean-up process all kind of other processes are also using the database and therefore maybe changing the database size. That probably explains the size difference.

But I’ll have another look at it.

Thanks for your feedback!

peace,
Rolf

hm, ok. that may be, but it’s not the case i have seen. I made a DB-dump, downloaded it, made the optimization with your plugin, made another DB-dump and simply compared the sizes. so, it is working well. but, the calculation shows allways the db-mb-number twice in the result page.

Datenbank-Gr??e
VORHER 5.672 MB
NACHHER 5.672 MB
Einsparungen bei diesem Lauf 0 KB
Einsparungen insgesamt seit dem ersten Lauf 0 KB

i do optimizations only after several works, so there are hundreds of revisitions deleted.

Hey arcticblue,

Are you using InnoDB tables?
They act differently with deleted data.

Try running the following query on your database, before and after the optimization:

SELECT table_schema "DB Name",
   Round(Sum(data_length + index_length), 0) "DB Size in B"
FROM   information_schema.tables
WHERE table_schema = 'xxx'
GROUP  BY table_schema

(replace ‘xxx’ with the name of the database you are optimizing)

Thanks,
Rolf

ok, i will/report.

sql results are:

5505024 before (5,25 MB exactly .. !?)
5472256 after (5,21875 MB)

plugin:

Datenbank-Gr??e
VORHER 5.25 MB
NACHHER 5.25 MB
Einsparungen bei diesem Lauf 0 KB
Einsparungen insgesamt seit dem ersten Lauf 0 KB

Hey arcticblue,

Thanks for checking!

I’ll have a closer look at it.

Rolf