How can I speed up my backoffice (very slow)?

[Thomas567]

Prestashop : 1.6.1.5

PHP 7

Mysql

bande passante : 100mbps

theme : template trip (mais ça me le faisait avec le thème par default) (I give you the template name but my problem occurs with the default template also).

 

 

 

 

Hi everyone,

 I send you this message because I wonder why 10sec are needed per loading page in the back-office. Every click on my prestashop backoffice is very slow.

On the navigator is quite ok. But on the left side, on the logo, an arrow turns to signify that prestashop load something.

And every manipulation, it takes a lot of time.

So I have a server on Hostinger and the speed is 100mbps. I could upgrade to 1000mbps. But I'm not sur that's helped the arrow to speed up the load.

I did a research last day. And I  found out that problem is due to ajax technology. 12 request are sent to the server every manipulation. But it's too request at the same time and the server could block the request to securize against DDOS attack. So Prestashop has to take a lapses of time to solve this problem (1sec per request).

So are you sur that problem is due to the DDOS security? How can you manage that? Have you the same problem?  

 

Thank you in advance!

 

Thomas

 

Salut à tous,

 

Je vous laisse un petit message pour vous demander si comme moi, vous avez 10sec de chargement à chaque fois que vous faites une manip sur le backoffice de prestashop.

La page en elle même se charge assez vite dans le navigateur mais c'est les petites flèches d'actualisations qui tournent qui sont lentes.

Mon serveur est un serveur mutualisé sous hostinger avec une bande passante de 100mbps.

Est-ce que passer en 1000mbps va booster ce chargement des flèches qui tournent?

J'ai cru comprendre que la techno sous prestashop était de l'ajax. Donc pour limiter un système de bloquage anti DDOS, Prestashop envoie une requete toutes les secondes pour charger ses pages de backoffice. Ayant une 10aine à envoyer, cela fait bien 10sec de chargement.

Je voulais savoir comment vous vivez cela? Si vous vous en accomodez? Déjà si vous avez ce problème? Si vous avez pu trouver une solution?

 

Merci!

Thomas

Edited April 29, 2016 by Thomas567 (see edit history)

[Oron]

Hello

 

Please here french Forum only in French langage, topic moved to English forum

[tuk66]

What URL?

[El Patron]

Please ensure all back office-->advanced parms-->performance are set for smarty, that smarty cache is enabled.

 

Most often someone will disable smart cache so they can see changes they make in front office, then forget to enable it.

[delphan]

Hi

 

My backoffice 1.6.1.6 is terribly slow. 

When I try to adjust product pages, I get a timeout, and the “save” button in not clickable (the wheel keeps turning).

 

This is what I did to try to solve it:

- performance panel - switched off third party modules

- performance panel - switched off combiniations and features

- checked the error logs: but no problems

- On the hosting side in Cpanel: changed the max_execution_time from 300 to 1000

- activated debug mode, but no problems found

 

But none of that worked.

In attachments the print screens of my performance page.

 

Can someone help?

[El Patron]

Hi

 

My backoffice 1.6.1.6 is terribly slow. 

When I try to adjust product pages, I get a timeout, and the “save” button in not clickable (the wheel keeps turning).

 

This is what I did to try to solve it:

- performance panel - switched off third party modules

- performance panel - switched off combiniations and features

- checked the error logs: but no problems

- On the hosting side in Cpanel: changed the max_execution_time from 300 to 1000

- activated debug mode, but no problems found

 

But none of that worked.

In attachments the print screens of my performance page.

 

Can someone help?

 

most of the issue with product editing was solved I think in 1.6.1.9.  It is not really possible to apply those patches too 1.6.1.6 unless you have mad skillz.  So please consider an upgrade using best practice methodolgy,  i.e. create dev copy run upgrade to see if you are able to upgrade correctly then go from there to a production implementation.