huge database on PS 8

[cpuin]

Hi,

 

I recently noticed that the database of my Prestashop 8.2.1 is huge - 5.19 GB

How to check what is generating such a huge amount of data?

Which logs or settings to disable?

[Daresh]

Start with logging in to phpMyAdmin and sort the columns descending by size, check which ones are the largest.

[Mediacom87]

Hi,

The subject has been discussed hundreds of times. This overload mainly comes from PrestaShop's statistical data, so you have three solutions:

1. Manually clearing problematic tables
2. Completely uninstall the statistics recovery module
3. Use a module that will automatically clean up for you

[PrestaHeroes.com]

Hi — this may help, and @Daresh is also correct.  now we discuss 101 times...loool
Using phpMyAdmin, you can sort your database by table size and row count to quickly identify which tables are growing abnormally. Without doing this, you are essentially guessing and won’t know where the actual bloat is coming from.

Be aware that some modules store caches and logs in database tables, and these can grow very large over time if not managed properly.

How to find large tables using phpMyAdmin:

Log in to phpMyAdmin from your hosting control panel.

Select your PrestaShop database from the left sidebar.

Click the Structure tab (this is the default view).

Scroll to the bottom of the table list and ensure the following columns are visible:

• Rows
• Data length
• Index length
• Size

Click the Size column header to sort tables by total size (Data + Index).

Alternatively, click Rows to sort by row count and identify log- or cache-heavy tables.

Tables that stand out as unusually large are typically the source of database growth and performance issues.

Here is an article that outlines common PrestaShop tables that tend to grow large, and which ones can typically be safely emptied or pruned (depending on your setup):

https://prestaheroes.com/blogs/mysql-optimization/which-large-prestashop-tables-can-be-dropped-or-emptied-safely

 

[musicmaster]

ps_layered_filter_block can become big too

[Ray UK]

ps_facetedsearch was the module that ate my database.

Without the cache enabled the db was <50MB, after enabling cache it jumps up to >3Gb in no time.

Ive left my ps_facetedsearch cache disabled for this very reason.