Jump to content

The joke about the infamous blocklayered


Recommended Posts

Yet again a customer complains about performances.

Let's look at the cause.

 

20 visitors/s means 20 create/drop/alter per seconds! (see attachment)

The server is a 16/32 cpu/thread, 196GB memory, SSD for the curious

 

TTFB:

Percentage of the requests served within a certain time (ms)
  50%   8502
  66%   8715
  75%   8850
  80%   8920
  90%   9186
  95%   9390
  98%   9943
  99%  11037
 100%  12433 (longest request)

Now let's disable blocklayered

Percentage of the requests served within a certain time (ms)
  50%    549
  66%    584
  75%    600
  80%    613
  90%    647
  95%    687
  98%    737
  99%    878
 100%   1032 (longest request)

It should be renamed BlockSlugishMyShop

 

post-41515-0-77693300-1460699178_thumb.png

  • Like 1
Link to comment
Share on other sites

Take a look into forge (and also into the forum - using google search). The speed problem for this module is known since some years... The module should be redesigned completely. Seems that no one developer has time for this ??

 

http://forge.prestashop.com/browse/PSCSX-1343

http://forge.prestashop.com/browse/NM-354

 

and so on.....

Link to comment
Share on other sites

I know that and even worst every new version is even more at putting server on its knews with no possibility for sysadmin to address the issue.

In the past I was creating a memory table at mysql startup and every user was using it now they discovered the memory engine but use it w/ non-sense.

 

We need a terabyte of server memory to serve pages in 20s ... so boring

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...