2 instances of prestashop: one catalog reference, one shop

[john74]

Hello,

 

I'm using prestashop (1.4.7.x) and I'm getting performances problems when I edit my product catalog while users are browsing the site (at least 1000 users a day). Problem comes from database locks.

 

I'm already having two instances of prestashop, one live for production, and one from development. I have no difficulties periodically copying everything from production to development.

 

In order to improve performances, I'm planning managing the catalog on a catalog instance, then copying periodically the whole catalog to the production environment. I guess it should work if I copy every catalog related table and if I never delete products that might have been ordered by customers.

 

Does anybody use such a strategy ?

Do you think it is worth a try ?

Do you see some potential problems that I'll have to manage ?

 

I'll report here my results.

 

Thank you for comments !

Edited September 11, 2012 by john74 (see edit history)

[El Patron]

Adding separate stand alone product catalogs sounds like a good solution at first but soon turns into a maint. nightmare. Just remember the old rule 'no duplicated data'.

 

And without looking at your site I would not readily agree that your bo performance has anything to do with file locking. For the simple reason and as far as I know, ps does not update a 'viewed' counter for products like a joomla or wp installation.

 

I'd concentrate on looking for any site performance issues especially as it concerns your mysql db. Phymyadmin has some nice reports that reports improvements in 'red'. We do offer a solution for spawning single installation catalogs, see my signature links.

 

Suerte!

Edited September 11, 2012 by elpatron (see edit history)