Jump to content

Slow backoffice and layered navigation 1.5.5.0 with BIG shop


Recommended Posts

I am looking for experiences with big stores and performance backoffice. I have 33.000 products and 200 categories with over 100.000 images and about 180.000 features.

 

 

In 1.5.5.0 the front office performance is good (a lot better then 1.5.4.1), however backoffice performance is slow, mostly when updating a product. e.g. Adding a price rule, changing picture, takes over 5 minutes to be processed.

 

Also Layered Navigation is impossible to configure, after 10 minutes I am able to save but the template is not stored in the database, so actually it doesn't work.

 

With smaller database I have none of these issues. Anyone with same problem and/or ways to fix this?

Link to comment
Share on other sites

I am currently on a shared hosting.

 

In my test environment on a dedicated PC I am experiencing some of the same problems, however, some things run faster.

 

Thanks for the article link, I will use it as I am planning to move to a dedicated platform which will hopefully solve most, if not all, of these problems.

 

People who have the same size of Prestashop and running well, I am interested in the hardware/software config specs.

Link to comment
Share on other sites

A dedicated pc is not the same as a dedicated server. I know on my pc, which is a intel 3770-k, 32 gb ram, and ssd drives, using xampp is a lot slower than the xeon server I use with 8gb ram. Web servers are optimized for serving on port 80 and processing scripts, our pcs are not really optimized for anything. They are jack of all trade machines so to speak. 

 

First thing I would do if I were you is try to trace the slow sql queries. If that does not seem to help, I would install the free tier of new relic and see what it comes up with. You will need at least a vps machine with ssh access to install it. You might be able to get your host to install it for you if you give them the license key that they give you. 

 

Also, in the back office you can enable debug profiling too, and it will show what is taking so long for the back office. My best guess off the cuff is it is the sql requests. It seems a lot of hosts farm out the sql to slow servers. Also, depending on the size of the vps / dedicated machine you use, you can cache the whole database in memory too. I read a pretty good article about maria db offering a memory / disk cached db. 

Link to comment
Share on other sites

  • 1 month later...

I am looking for experiences with big stores and performance backoffice. I have 33.000 products and 200 categories with over 100.000 images and about 180.000 features.

 

 

In 1.5.5.0 the front office performance is good (a lot better then 1.5.4.1), however backoffice performance is slow, mostly when updating a product. e.g. Adding a price rule, changing picture, takes over 5 minutes to be processed.

 

Also Layered Navigation is impossible to configure, after 10 minutes I am able to save but the template is not stored in the database, so actually it doesn't work.

 

With smaller database I have none of these issues. Anyone with same problem and/or ways to fix this?

Hello,

I don't know if you solved but disabling mod_security maybe the solution.

In the backoffice go to  preference > URL & SEO > disable Apache mod_security  > yes

Link to comment
Share on other sites

×
×
  • Create New...