Jump to content

Database size


CJH

Recommended Posts

I have a problem that I think is database related. Prestashop is v1.6.0.6.

 

I found that the db backup started to fail with an error that it could not find a schema for one table. I also had problems with a PrestaBackUP module that failed to complete, apparently timing out. Finding other reports suggested this might relate to the size of the database.

 

The shop has only been online for a few months, with 300 orders placed, so not that many and not a huge site. But the database was 108Mb (compressed to 16Mb if backed up as .gz direct from phpMyAdmin). I tried to find out exactly what the Prestashop Cleaner module did with 'Database Cleaning', failed to locate information and ended up trying it. This reported removing 24 lines (only) from ps_cart.

 

But I found huge numbers in the guest table - 65,000 of them - that had no attached data and I assume relate to robots. I deleted these as well as stats information in connections etc using a free module from catalogo-onliners that said 'This option delete all the fields from connections/expired vouchers/cart tables and optimize all tables'. It reported removing about another 65,000 entries.

 

The database dropped from 108Mb to 91Mb, which still seems h

uge. db Backup still fails to run.

 

Is there anything else to try to make the database smaller? Is the database size related to the db Backup module not working, and how can its operation be repaired?

Edited by CJH (see edit history)
Link to comment
Share on other sites

I used the db Backup under Advanced Parameters in Prestashop; this now fails with an error: 'unable to obtain scheme of ps_carrier'. I've seen other reports (for different table names) with a suggestion that such a failure is linked with a large database, but beyond this I don't know. It used to work.

 

Using phpMyAdmin / Export works fine.

 

cPanel - apologies, but I don't know what or where this is. Sounds like Control Panel, but I don't know where ...

 

I have an independent module for backups; this fails to complete.

 

It's also the size of the database that concerns me - and the speed at which entries are made to this by 'visitors' which I presume are robots. These run at around 100 per hour, each adding a line to the database with (mostly) zero data. Is there any way to slow this addition down? Or to decrease the overall size of the database? Or is this size of 91Mb, after removing statistic table entries, normal?

Link to comment
Share on other sites

×
×
  • Create New...