Hi Mike!
The increase in database size is expected given how WordPress works. For example, updating a post (including renaming it) leads to the creation of post revisions which are saved as new rows in the relevant database table. Likewise, deleting a user may leave behind related data like comments, postmeta, usermeta and other relevant information. Scheduled actions may also be created against a future date, thus causing some data to only be permanently removed at a later time.
There are many other potential reasons for such database size increase and a quick Google search will definitely provide relevant results.
Feel free to get in touch if you have any further concerns pertaining to the WPO plugin.
Kind regards.
Thanks Damilare for response.
Just want to clarify. When I run the full optimization..it doesn’t lower the number….are you saying that over time the memory “will be freed up” and subsequent Optimization runs will eventually reduce the total memory count?
Thanks
Running full optimization does not necessarily mean space will be freed instantly all the time. This is largely dependent on MySQL storage engine behavior.
For example, deleting a row of data in an InnoDB table may still retain allocated space for some time until the table shrinks when the OPTIMIZE TABLE sql query is run either manually or at a scheduled time.
Also, the amount of data optimized each time may not be significant enough (a few kilobytes) to reflect in your monitoring endeavors.
In any case, WPO database optimization feature will always do its job in its optimization operations provided there is something to optimize, as listed in the optimization table.
Kind regards.
