Prestashop 8.2.1 database size increasing too much due to analytics or visit tables

[JM]

error multiple posts.

delete.

Edited April 29, 2025 by JM (see edit history)

[hoodiecoloss]

You must match them layer by layer, but there is no prescribed sequence; you may match any layer at your discretion. It facilitates the process, allowing for the puzzle to be completed swiftly.

[leahpowell]

Got it, that makes sense. Matching them layer by layer without a fixed order definitely gives more flexibility and speeds things up. Thanks for clarifying the approach—it sounds like a practical way to handle the puzzle.

[cooper662]

eah, that’s actually a common issue in Prestashop 8.2.1. The database size often grows quickly because of the ps_connections, ps_connections_source, and ps_guest tables — they store visit and analytics data. Over time, these tables can become huge, especially if your site gets regular traffic.

You can safely clean them up by truncating or deleting old records (after making a backup first). Also, consider disabling “Save page views” or “Save statistics” in the Back Office if you don’t really need that data.

A good routine cleanup with a cron job or module that manages database optimization can also help keep the size under control.

[PrestaHeroes.com]

I build basic blog on how to clean up common large tables but pretty much what @cooper662 suggested

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