Large overhead | ww.wp.xz.cn

Resolved NOT-IN-USE-DELETE
(@rogerwheatley)

12 years, 8 months ago

What can we do to fix the large database overhead each rule costs?
For example, creating one rule causes the following:

Table:
wp_psn_rules

Table Records:
1

Data Usage:
16.0 KiB

Index Usage:
0

Overhead:
6.0 MiB

In essence, it appears there’s a 6MB overhead for a single 16KB record.

Any assistance would be greatly appreciated! 🙂

http://ww.wp.xz.cn/plugins/post-status-notifier-lite/

Viewing 2 replies - 1 through 2 (of 2 total)

Plugin Author Timo
(@worschtebrot)

12 years, 8 months ago

Hi Roger,
thanks for your feedback. I’ll check this on my test servers and give you a reply. Any more information would be great (eg screenshots). Please use the contact or support form on http://www.ifeelweb.de/contact/
Thanks

Plugin Author Timo
(@worschtebrot)

12 years, 8 months ago

I did some research and can not find any negative aspect about this. Eg all the tables on my dev WP installation have a “Data_free” value of 6291456, including the psn_rules table.
You get those data with SQL “SHOW TABLE STATUS” (see http://dev.mysql.com/doc/refman/5.0/en/show-table-status.html)

Only phpMyAdmin calls this value “overhead” which sounds kind of bad.

http://stackoverflow.com/questions/1288573/how-much-table-overhead-is-too-much:
“Overhead” is not yet reclaimed space formerly occupied by now deleted records. If you’re doing a lot of inserts / deletes, it’s pretty much always going to be there.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Large overhead’ is closed to new replies.

2 replies
2 participants
Last reply from: Timo
Last activity: 12 years, 8 months ago
Status: resolved