I have noticed that Webprofiler db storage table reaches huge dimensions quickly and easy ... after its activation,
also on a just installed (and quite empty) Drupal site/build.

The default Webprofiler setup uses the Database as Storage backend, and would/should delete its data during cache clear. Is this right?
But just few application pages surfing would make the webprofiler db table (and the all Drupal database dump) around (and even more) than 100 mb.
This might be worth, due the great amount of data this module is intercepting, but would be probably better to warn the user about all this,
and would be either nice to implement (if possible and really worth to) a better control of its storage process and techniques.

Just minding about the following possibile options:

- warning to the user about this great amount of stored data (during the module activation/enabling phase and/or in the status report page?),
and the possibility to properly tune his preferred storage process, with the following options ...
- a cache/cron controlled technique that might clean the db table and transfer the split/incremental webprofiler monitored data in zipped/compressed pockets into timestamped files ...
- a db or files size limit controlled process, to accomplish the same previous task

Just to put some possible ideas on this table ;-)

Comments

itamair created an issue. See original summary.

itamair’s picture

itamair CreditAttribution: itamair commented
Issue summary: View changes
pheraph’s picture

pheraph CreditAttribution: pheraph commented

Came here, because I noticed the very same effect on the database size. A maintenance solution would be greatly appreciated. :-)

hassengh’s picture

hassengh CreditAttribution: hassengh commented

it is correct : truncate tabe webprofiler ??

lussoluca’s picture

lussoluca
he/him
Primary language Italian
Location Italy
CreditAttribution: lussoluca commented

yes a quick solution is to truncate the webprofiler table

hassengh’s picture

hassengh CreditAttribution: hassengh commented

thanks , also in clear cache this table truncate automatically

sher1’s picture

sher1 CreditAttribution: sher1 as a volunteer and at Brigham Young University commented

I just wanted to mention that there was so much data being stored in our webprofiler table that our database backups were failing because they couldn't finish. After truncating the webprofiler table, It had inserted another 175MB of data in 2 minutes. Once we uninstalled the module, the total site backup was 55MB. Prior, it ran out of space but couldn't finish at 16GB. There needs to be some configuration of this to disable storing all that data. Having said that, it is VERY useful data and I really like having it on my website except for the huge impact it had on backups.

fgm’s picture

fgm
Primary language French
Location Paris, France
CreditAttribution: fgm as a volunteer and at OSInet commented

I think your simplest option is to go to admin/config/development/devel/webprofiler and switch the storage from database to file.

hassengh’s picture

hassengh CreditAttribution: hassengh commented

@fgm thank you , it is best solution

firewaller’s picture

firewaller CreditAttribution: firewaller commented

This caused a major issue on my production site since it bloated the mySQL server disk space to capacity and prevented mySQL from starting. I had to increase the server space temporarily, reboot mySQL, drop the table, and disable the module. I suppose you could also just wipe the webprofiler.ibd file, but I don't know whether that involves other steps.

Although moving the storage from database to files would prevent mySQL crashes you might max out your disk spaces or accrue unnecessary charges though your host. I'd suggest adding a warning and preventing the table/file from getting too large.

fgm’s picture

fgm
Primary language French
Location Paris, France
CreditAttribution: fgm as a volunteer and at OSInet commented

In the meantime, wouldn't we want to use files by default, for safety ?