Site is running painfully slow, large database

[neller]

Hi,

 

I have a site that has a very large database (over 30,000 categories and will have 90,000 products).

 

It is hosted on a VPS, but it seems that prestashop can't handle such a large amount of data.

 

Is there a maximum amount of categories & products that can be used or is the server inadequate?

 

Server spec;

2 Cores

2Gb Ram

50Gb HDD

CentOS 6

PHP spec can be seen here - http://92.60.127.192/~mailorde/info.php'>http://92.60.127.192/~mailorde/info.php

 

Prestashop version 1.5.4.1

Advanced Parameters > Performance;

Recompile templates if the files have been updated,

Cache - Yes,

Combinations - No,

Features - Yes,

CCC - all options set to original

Ciphering Algorithm - Use Rijndael with mcrypt lib.

Use Cache - Xcache

 

 

The site is currently running of a temp url of http://92.60.127.192/~mailorde/ if you want to see how slow it actually is.

 

Does anyone have any suggestions that might increase the speed for this?

Any suggestions are welcome.

 

Neller

[Dh42]

Its not so much that Prestashop cannot handle it. In this situation think of Prestashop as a big semi trailer and all of your categories and products being the cargo. Now think of the small car (vps account) you are trying to pull it with.

 

 

Long story short, you need a better hosting package like a dedicated server.

[neller]

Thanks for the reply.

I have since then upped the spec to use 5 cores instead of two.

Are you versed enough to point me in the direction of what server spec I should be aiming at?

[bellini13]

personally i don't think resources are the problem, unless you have a lot of visitors. Being that this is a test site (temp url), I suspect you are not running into CPU and memory constraints.

 

If a single user is hitting the site, and you are experiencing bad performance, then you have either a configuration issue with apache/php/mysql, or you have a an ineffective caching, or an issue with Prestashop.

 

I would try to disable any modules/blocks that are displaying the categories (like a top menu, or blockcategory) and see if the issue is resolved. There are known issues with this modules and you may be hitting an upper limit of what they can support.

[Dh42]

My guess about resources is that when sql is browsing the categories. 30k is a lot of categories to browse. Debug profiling could confirm the slower queries I assume.