Excessive Database Usage

Ouch!

No index : ok it is normal
100 bytes by record seems to be ok too according to fields.

I don’t know what os the 702 Mib overhead but it is really huge !!!

You can manually clean this table in the s2member Secure File Browser admin panel > Settings > General. Click on the button [Delete All Records…]. When deleting, the plugin will suggest backuping data in CSV or XML.

Then, in the s2member Secure File Browser admin panel > Settings > General, you can set a retention limit for this table (duration or maximum number of lines).

Tell me it the overhead decreases…

??
deleting doesn’t help. The overhead stays – actually now: wp_psk_s2msfb_downloads 0 16.0 KiB 0 bytes 703.0 MiB

The backup downloaded before deletion as xml is only 227KB. Due to client data I don#t want to publish it!

Ok, more informations about the overhead here :

https://stackoverflow.com/questions/565997/in-mysql-what-does-overhead-mean-what-is-bad-about-it-and-how-to-fix-it

It is strange, I have no overhead in any wordpress installation.

Do you have import database ? Does the optimization help ?

I have no overhead in any other plugin/entry of my database. Optimize doesn’t help – here’s a screenshot:

hmm – link not visible: https://www.velomap.org/database_velomap.png

Okay, now I dropped the entry – Overhead is gone. Emptying the table, did not fix it.

I will have to do the same on my second website – where I have exactly the same problem with overhead.

Well – I tried around a bit more. As soon as I install it – I get this excessive overhead. No need to have any data recorded yet.

Really strange… The only difference I can see is the mysql engine version. You run 5.5.25 when I run the community version 5.5.17.

1. Can you DROP the table wp_psk_s2msfb_downloads please ?

2. And then create it manually :

CREATE TABLE wp_psk_s2msfb_downloads (
id INT(11) NOT NULL AUTO_INCREMENT,
created TIMESTAMP NOT NULL,
userid BIGINT(20) NOT NULL,
useremail VARCHAR(100) NOT NULL,
ip VARCHAR(100) NOT NULL,
filepath VARCHAR(4000) NOT NULL,
filemd5 VARCHAR(32) NOT NULL,
notified TIMESTAMP,
PRIMARY KEY (id)
) DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

3. If it does not change anything, could try again with this CREATE statement please ? (just change the mysql engine type)

CREATE TABLE wp_psk_s2msfb_downloads (
id INT(11) NOT NULL AUTO_INCREMENT,
created TIMESTAMP NOT NULL,
userid BIGINT(20) NOT NULL,
useremail VARCHAR(100) NOT NULL,
ip VARCHAR(100) NOT NULL,
filepath VARCHAR(4000) NOT NULL,
filemd5 VARCHAR(32) NOT NULL,
notified TIMESTAMP,
PRIMARY KEY (id)
) ENGINE=MyISAM DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

4. Finally, can you try this next to drop and re-create :

ALTER TABLE wp_psk_s2msfb_downloads ADD INDEX ( created ) ;
ALTER TABLE wp_psk_s2msfb_downloads ADD INDEX ( userid ) ;

Thanks – 2. Just directly created big overhead again.
3. Works without overhead.

I just kept the engine, I don’t know which engine is opensuse default – or better which engine I’m using.

Do I need to do 4. as well for testing?

Hello,

good news for point 3 so I will force MyISAM engine in the next release but it is still strange…

No problem for point 4, we do not really need indexes on this table.

Thank you for your patience !

potsky