Page load time (time to first byte) and REQ/s

nashtu3000 · February 2, 2012

It seems that my prestashop refuses to go above 6 req/seq in a simple ab test.

ab -n 50 -c 3 http://tigariieftine.ro/

Anyone with a similar issue?

Here's my config:

I am running on a VPS with 1 Core and 1024 RAM.

I also have ttfb problems. I can't seem to get decent loading times, i've tried everything.

Can someone help me?

Edit: adding config info:

Edited February 2, 2012 by nashtu3000 (see edit history)

El Patron · February 2, 2012

your ttfb numbers for dynamic content look ok. 250 ms time frames

and your site loaded here in Medellin, nicely (fast).

are you using file cache? your screen shots are too short to see what cache system.

nashtu3000 · February 3, 2012

If i enable memcache or filecache the site slows down and the ab REQ/sec slow down even further. What do you get for ab tests with your prestashop?

Is 4 req/s a normal number? I find it to be very low and i've run out of optimisation ideeas.

El Patron · February 3, 2012

I also on vps get around 250ms. From all I read this is typcial and to improve any further requires hardware upgrades and things like moving mysql to a different server etc. There are some very good threads on the forum on how to increase the mysql performance by tweaking some of the calls.

Suerte!

nashtu3000 · February 3, 2012

Mysql is running perfectly, everything is in the query cache, this isn't related to mysql. I also have slow q logging enabled for any queries and it's running as smoothly as possible.

The problem are the requests/sec which can't be any lower. I am getting 200 req/sec on images and on phpinfo() style pages, the difference is insane (200 req/s compared to 6 req/s) so that's why i am thinking there's something i am missing.

With this in mind, if i have 6 simultaneous visitors on the site the performance drops almost to a halt. Is that what everyone using prestashop should experience .. ?

El Patron · February 3, 2012

jajajaja...mysql is running perfectly...if that was true there wouldn't be paid releases...query cache......last time I looked at query cache it filed updates immediate, i.e. not a write cache...with updates only on x updates or time...I just looked (I did not want to) at my mysql runtime statistics...plenty of work for a vanilla install to improve several area's of operation. someday.

I've seen several posts about turning off prestashop statics that signficantly improves performance...as it is somewhat redundant if you are using google analytics...

Suerte!

nashtu3000 · February 3, 2012

jajajaja...mysql is running perfectly...if that was true there wouldn't be paid releases...query cache......last time I looked at query cache it filed updates immediate, i.e. not a write cache...with updates only on x updates or time...I just looked (I did not want to) at my mysql runtime statistics...plenty of work for a vanilla install to improve several area's of operation. someday.

Well it works from the point of view that it doesn't have slow queries, so mysql is not the issue here. I can also enable memcached which should relieve most of the stress that the db server gets. In fact i've done that already and i haven't seen any change in performance when tested with ab or similar tools.

You did not answer my question, how many req/s does your presta install output? I'm starting to think that i've reached a maximum of optimisation on this since i can't find any other issues with it. But 6 req/s is still pathetic...

I've seen several posts about turning off prestashop statics that signficantly improves performance...as it is somewhat redundant if you are using google analytics...

Done that already, no changes..

El Patron · February 3, 2012

which tool are using to measure your req/s? I'll try it on a couple differnt sites and let you know.

And I don't understand how you can rule out mysql, ps of course is a database driven website and will make calls each and every page serve for many foolish things. You have 'no' red's in your mysql runtime configuation? If I were to take time to chase the little red's to improve mysql I'd get nothing else done.

nashtu3000 · February 3, 2012

I am using ab - http://httpd.apache....rograms/ab.html it's standard on any linux. And it's the industry's mainstream tool for benchmarking req/s and response times.

Here's what i have for mysql using mysqltuner.pl, a global recognized script that analyzes the mysql status and reports on any problems found:

root@server /]# perl mysqltuner.pl -user root -pass ****
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").

>>  MySQLTuner 1.2.0 - Major Hayden <[email protected]>
>>  Bug reports, feature requests, and downloads at http://mysqltuner.com/
>>  Run with '--help' for additional options and output filtering
[OK] Logged in using credentials passed on the command line

-------- General Statistics --------------------------------------------------
[--] Skipped version check for MySQLTuner script
[OK] Currently running supported MySQL version 5.5.16-log
[OK] Operating on 32-bit architecture with less than 2GB RAM

-------- Storage Engine Statistics -------------------------------------------
[--] Status: +Archive -BDB -Federated +InnoDB -ISAM -NDBCluster
[--] Data in MyISAM tables: 1M (Tables: 527)
[--] Data in InnoDB tables: 64K (Tables: 4)
[--] Data in PERFORMANCE_SCHEMA tables: 0B (Tables: 17)
[!!] Total fragmented tables: 4

-------- Security Recommendations  -------------------------------------------
[OK] All database users have passwords assigned

-------- Performance Metrics -------------------------------------------------
[--] Up for: 22h 3m 29s (1M q [21.811 qps], 8K conn, TX: 897M, RX: 305M)
[--] Reads / Writes: 99% / 1%
[--] Total buffers: 144.0M global + 6.2M per thread (50 max threads)
[OK] Maximum possible memory usage: 453.4M (44% of installed RAM)
[OK] Slow queries: 0% (0/1M)
[OK] Highest usage of available connections: 10% (5/50)
[OK] Key buffer size / total MyISAM indexes: 32.0M/2.4M
[OK] Key buffer hit rate: 100.0% (1M cached / 293 reads)
[OK] Query cache efficiency: 95.8% (1M cached / 1M selects)
[!!] Query cache prunes per day: 43152
[OK] Sorts requiring temporary tables: 0% (0 temp sorts / 7K sorts)
[OK] Temporary tables created on disk: 14% (102 on disk / 682 total)
[OK] Thread cache hit rate: 99% (5 created / 8K connections)
[OK] Table cache hit rate: 98% (586 open / 593 opened)
[OK] Open file limit used: 1% (1K/65K)
[OK] Table locks acquired immediately: 100% (180K immediate / 180K locks)
[OK] InnoDB data size / buffer pool: 64.0K/32.0M

-------- Recommendations -----------------------------------------------------
General recommendations:
Run OPTIMIZE TABLE to defragment tables for better performance
MySQL started within last 24 hours - recommendations may be inaccurate
Variables to adjust:
query_cache_size (> 32M)

[root@server /]#

PS: just bumped the qcachesize to 128m so i should get a more accurate stat of the prunes/day by tomorrow.

Edit: adding the ab result here:

ab -n 50 -c 3 http://tigariieftine.ro/
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking tigariieftine.ro (be patient).....done

Server Software:	    Apache
Server Hostname:	    tigariieftine.ro
Server Port:		    80
Document Path:		  /
Document Length:	    30117 bytes
Concurrency Level:	  3
Time taken for tests:   9.125 seconds
Complete requests:	  50
Failed requests:	    0
Write errors:		   0
Total transferred:	  1546336 bytes
HTML transferred:	   1505850 bytes
Requests per second:    5.48 [#/sec] (mean)
Time per request:	   547.495 [ms] (mean)
Time per request:	   182.498 [ms] (mean, across all concurrent requests)
Transfer rate:		  165.49 [Kbytes/sec] received
Connection Times (ms)
		  min  mean[+/-sd] median   max
Connect:	   46  514 104.3    506	 804
Processing:	 0   30 104.3	  0	 648
Waiting:	    0    9  60.8	  0	 430
Total:	    431  543 106.3    528    1051
Percentage of the requests served within a certain time (ms)
 50%    528
 66%    552
 75%    567
 80%    592
 90%    672
 95%    695
 98%   1051
 99%   1051
100%   1051 (longest request)

El Patron · February 3, 2012

Hi, thanks so ever much for turning me on to new knowledge!

I have so little data on my sites I am not sure posting my data is of much help:

ab -n 50 -c 3

Server Software:		Apache/2.2.3
Server Hostname:		www.demov1462.domain.co
Server Port:			80
Document Path:		  /
Document Length:		0 bytes
Concurrency Level:	  3
Time taken for tests:   0.972544 seconds
Complete requests:	  50
Failed requests:		0
Write errors:		   0
Non-2xx responses:	  50
Total transferred:	  37378 bytes
HTML transferred:	   0 bytes
Requests per second:	51.41 [#/sec] (mean)
Time per request:	   58.353 [ms] (mean)
Time per request:	   19.451 [ms] (mean, across all concurrent requests)
Transfer rate:		  37.02 [Kbytes/sec] received
Connection Times (ms)
		  min  mean[+/-sd] median   max
Connect:		0	0   0.0	  0	   0
Processing:	50   56   4.0	 57	  68
Waiting:	   50   56   3.7	 56	  65
Total:		 50   56   4.0	 57	  68
Percentage of the requests served within a certain time (ms)
 50%	 57
 66%	 58
 75%	 59
 80%	 60
 90%	 62
 95%	 64
 98%	 68
 99%	 68
100%	 68 (longest request)

nashtu3000 · February 3, 2012

It looks like you're pinging a null page. Here's a real result for your site.. you should be worried about it because you're very very low on req/s

ab -n 50 -c 3 http://demov1462.etiendas.co/en/music-ipods/1-ipod-nano.html
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking demov1462.etiendas.co (be patient).....done

Server Software:	    Apache/2.2.3
Server Hostname:	    demov1462.etiendas.co
Server Port:		    80
Document Path:		  /en/music-ipods/1-ipod-nano.html
Document Length:	    34630 bytes
Concurrency Level:	  3
Time taken for tests:   25.104 seconds
Complete requests:	  50
Failed requests:	    0
Write errors:		   0
Total transferred:	  1793972 bytes
HTML transferred:	   1731500 bytes
Requests per second:    1.99 [#/sec] (mean)
Time per request:	   1506.228 [ms] (mean)
Time per request:	   502.076 [ms] (mean, across all concurrent requests)
Transfer rate:		  69.79 [Kbytes/sec] received
Connection Times (ms)
		  min  mean[+/-sd] median   max
Connect:	  172 1423 295.7   1439    2585
Processing:	 0   62 201.3	  2    1308
Waiting:	    0   14 101.9	  0	 720
Total:	   1266 1485 237.5   1464    2585
Percentage of the requests served within a certain time (ms)
 50%   1464
 66%   1475
 75%   1494
 80%   1524
 90%   1805
 95%   2047
 98%   2585
 99%   2585
100%   2585 (longest request)

nashtu3000 · February 5, 2012

Anyone else care to join with their pretashop req/s results?

borescopeit · February 5, 2012

Anyone else care to join with their pretashop req/s results?

I just installed fresh install of 1.5.0.3 on my dedicated server. Apache MPM worker module, fcgid, suhosin + xcache enabled in the caching settings of presta. Here is my test output:

root@zzz:/# ab -n 50 -c 3 http://borescopeit.com/ru/
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking borescopeit.com (be patient).....done
Server Software:		Apache
Server Hostname:		borescopeit.com
Server Port:			80
Document Path:		  /ru/
Document Length:		32940 bytes
Concurrency Level:	  3
Time taken for tests:   4.157 seconds
Complete requests:	  50
Failed requests:		0
Write errors:		   0
Total transferred:	  1701702 bytes
HTML transferred:	   1647000 bytes
Requests per second:	12.03 [#/sec] (mean)
Time per request:	   249.411 [ms] (mean)
Time per request:	   83.137 [ms] (mean, across all concurrent requests)
Transfer rate:		  399.78 [Kbytes/sec] received
Connection Times (ms)
		  min  mean[+/-sd] median   max
Connect:		0	1   0.1	  1	   1
Processing:   204  244 112.7	218	 687
Waiting:	  203  243 112.7	217	 686
Total:		205  245 112.8	218	 688
Percentage of the requests served within a certain time (ms)
 50%	218
 66%	220
 75%	221
 80%	223
 90%	227
 95%	684
 98%	688
 99%	688
100%	688 (longest request)

Better than yours, guys, but I need over 50 concurrent requests served simultaneously with Presta. Here is my CS-CART with 200 products benchmark. It is heavier loader, and it completely fails the test:

root@zzz:/# ab -n 50 -c 3 http://borescopeit.org/
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking borescopeit.org (be patient).....done

Server Software:		Apache
Server Hostname:		borescopeit.org
Server Port:			80
Document Path:		  /
Document Length:		168743 bytes
Concurrency Level:	  3
Time taken for tests:   9.913 seconds
Complete requests:	  50
Failed requests:		48
  (Connect: 0, Receive: 0, Length: 48, Exceptions: 0)
Write errors:		   0
Total transferred:	  8471596 bytes
HTML transferred:	   8442296 bytes
Requests per second:	5.04 [#/sec] (mean)
Time per request:	   594.752 [ms] (mean)
Time per request:	   198.251 [ms] (mean, across all concurrent requests)
Transfer rate:		  834.60 [Kbytes/sec] received
Connection Times (ms)
		  min  mean[+/-sd] median   max
Connect:		0	1   0.1	  1	   1
Processing:   506  570  42.8	559	 676
Waiting:	  418  495  47.7	479	 592
Total:		507  571  42.8	560	 676
Percentage of the requests served within a certain time (ms)
 50%	560
 66%	601
 75%	603
 80%	608
 90%	631
 95%	649
 98%	676
 99%	676
100%	676 (longest request)

Here is a bit heavier requests report on Presta and CS-CART following:

root@zzz:/# ab -n 200 -c 10 http://borescopeit.com/ru/
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking borescopeit.com (be patient)
Completed 100 requests
Completed 200 requests
Finished 200 requests

Server Software:	    Apache
Server Hostname:	    borescopeit.com
Server Port:		    80
Document Path:		  /ru/
Document Length:	    32940 bytes
Concurrency Level:	  10
Time taken for tests:   22.438 seconds
Complete requests:	  200
Failed requests:	    0
Write errors:		   0
Total transferred:	  6806702 bytes
HTML transferred:	   6588000 bytes
Requests per second:    8.91 [#/sec] (mean)
Time per request:	   1121.910 [ms] (mean)
Time per request:	   112.191 [ms] (mean, across all concurrent requests)
Transfer rate:		  296.24 [Kbytes/sec] received
Connection Times (ms)
		  min  mean[+/-sd] median   max
Connect:	    0  647 1532.4	  1    9021
Processing:   196  326 369.4    223    2333
Waiting:	  195  325 369.4    222    2331
Total:	    196  973 1530.9    242    9239
Percentage of the requests served within a certain time (ms)
 50%    242
 66%    390
 75%    455
 80%   2240
 90%   3226
 95%   3233
 98%   3246
 99%   9220
100%   9239 (longest request)

-----------------------------
CS-CART
root@zzz:/# ab -n 200 -c 10 http://borescopeit.org/
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking borescopeit.org (be patient)
Completed 100 requests
Completed 200 requests
Finished 200 requests

Server Software:	    Apache
Server Hostname:	    borescopeit.org
Server Port:		    80
Document Path:		  /
Document Length:	    168777 bytes
Concurrency Level:	  10
Time taken for tests:   30.941 seconds
Complete requests:	  200
Failed requests:	    199
  (Connect: 0, Receive: 0, Length: 199, Exceptions: 0)
Write errors:		   0
Total transferred:	  33887100 bytes
HTML transferred:	   33769900 bytes
Requests per second:    6.46 [#/sec] (mean)
Time per request:	   1547.069 [ms] (mean)
Time per request:	   154.707 [ms] (mean, across all concurrent requests)
Transfer rate:		  1069.53 [Kbytes/sec] received
Connection Times (ms)
		  min  mean[+/-sd] median   max
Connect:	    0    1   0.2	  1	   2
Processing:   545 1534 962.7    993    4000
Waiting:	  452 1317 922.5    745    3828
Total:	    546 1535 962.8    993    4001
Percentage of the requests served within a certain time (ms)
 50%    993
 66%   2247
 75%   2540
 80%   2627
 90%   2890
 95%   3089
 98%   3951
 99%   3994
100%   4001 (longest request)

Edited February 5, 2012 by borescopeit (see edit history)

El Patron · February 5, 2012

Please excuse me, I have my demo doing force compiles and cache off for module testing. Here is the test with forced compiles off and cache enabled. I am not at this time running memcache nor file system.

This is a base 1.4.6.2 with new_theme running on a VPS. Looks like I have work to do.

Server Software:		Apache/2.2.3
Server Hostname:		demov1462.etiendas.co
Server Port:			80
Document Path:		  /en/music-ipods/1-ipod-nano.html
Document Length:		34569 bytes
Concurrency Level:	  3
Time taken for tests:   8.300922 seconds
Complete requests:	  50
Failed requests:		0
Write errors:		   0
Total transferred:	  1790878 bytes
HTML transferred:	   1728450 bytes
Requests per second:	6.02 [#/sec] (mean)
Time per request:	   498.055 [ms] (mean)
Time per request:	   166.018 [ms] (mean, across all concurrent requests)
Transfer rate:		  210.58 [Kbytes/sec] received
Connection Times (ms)
		  min  mean[+/-sd] median   max
Connect:		0	0   0.0	  0	   0
Processing:   404  487 188.8	434	1541
Waiting:	  404  484 188.6	432	1541
Total:		404  487 188.8	434	1541
Percentage of the requests served within a certain time (ms)
 50%	434
 66%	450
 75%	462
 80%	470
 90%	570
 95%	941
 98%   1541
 99%   1541
100%   1541 (longest request)

nashtu3000 · February 6, 2012

@borescopeit how does xcache compare with apc? I'm using apc and it seems to work very well..

@elpatron do you have any php opcode cache installed?

@ANYONE who has some decent performance with prestashop? I mean industry-wise decent performance and not what we're getting now. What other tricks are there to speed it up? It's slow as hell..

El Patron · February 6, 2012

@elpatron do you have any php opcode cache installed?

No. I've looked at it but until our business get's going a little bit I've concentrated on less fun things.

nashtu3000 · February 13, 2012

Switched the vpn.. Stats suck here as well even tough i now have 3GHZ proc and 2GB Ram instead of 1GHZ and 1GB..

ab -n 200 -c 3 http://tigariieftine.com/
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking tigariieftine.com (be patient)
Completed 100 requests
Completed 200 requests
Finished 200 requests

Server Software:	    Apache
Server Hostname:	    tigariieftine.com
Server Port:		    80
Document Path:		  /
Document Length:	    28500 bytes
Concurrency Level:	  3
Time taken for tests:   31.980 seconds
Complete requests:	  200
Failed requests:	    0
Write errors:		   0
Total transferred:	  5861594 bytes
HTML transferred:	   5700000 bytes
Requests per second:    6.25 [#/sec] (mean)
Time per request:	   479.695 [ms] (mean)
Time per request:	   159.898 [ms] (mean, across all concurrent requests)
Transfer rate:		  179.00 [Kbytes/sec] received
Connection Times (ms)
		  min  mean[+/-sd] median   max
Connect:	    7  471 196.8    428    1674
Processing:	 0    7  45.9	  1	 441
Waiting:	    0    4  43.9	  0	 441
Total:	    207  479 190.6    442    1676
Percentage of the requests served within a certain time (ms)
 50%    442
 66%    518
 75%    593
 80%    635
 90%    730
 95%    798
 98%    937
 99%    947
100%   1676 (longest request)

Any ideas on improving presta's performance?

DutchCoding · March 4, 2012

Switched the vpn.. Stats suck here as well even tough i now have 3GHZ proc and 2GB Ram instead of 1GHZ and 1GB..

ab -n 200 -c 3 http://tigariieftine.com/
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking tigariieftine.com (be patient)
Completed 100 requests
Completed 200 requests
Finished 200 requests

Server Software:		Apache
Server Hostname:		tigariieftine.com
Server Port:			80
Document Path:		  /
Document Length:		28500 bytes
Concurrency Level:	  3
Time taken for tests:   31.980 seconds
Complete requests:	  200
Failed requests:		0
Write errors:		   0
Total transferred:	  5861594 bytes
HTML transferred:	   5700000 bytes
Requests per second:	6.25 [#/sec] (mean)
Time per request:	   479.695 [ms] (mean)
Time per request:	   159.898 [ms] (mean, across all concurrent requests)
Transfer rate:		  179.00 [Kbytes/sec] received
Connection Times (ms)
		  min  mean[+/-sd] median   max
Connect:		7  471 196.8	428	1674
Processing:	 0	7  45.9	  1	 441
Waiting:		0	4  43.9	  0	 441
Total:		207  479 190.6	442	1676
Percentage of the requests served within a certain time (ms)
 50%	442
 66%	518
 75%	593
 80%	635
 90%	730
 95%	798
 98%	937
 99%	947
100%   1676 (longest request)

Any ideas on improving presta's performance?

Hey,

After some extensive testing I concluded that the best way to double your performance is to get a vps with 2 cores and 1024mb ram

I get about 11 - 15 on that setup.

P.S. turning off the css js and html compression in prestashop backoffice speeds your up on benchmarking. but sometimes can have adverse effect on real users.

Greetingz,

Dutchcoding

DutchCoding · March 6, 2012

Document Path: /presta/prices-drop.php

Document Length: 20183 bytes

Concurrency Level: 200

Time taken for tests: 9.809 seconds

Complete requests: 200

Failed requests: 0

Write errors: 0

Total transferred: 4178542 bytes

HTML transferred: 4036600 bytes

Requests per second: 20.39 [#/sec] (mean)

Time per request: 9809.106 [ms] (mean)

Time per request: 49.046 [ms] (mean, across all concurrent requests)

Transfer rate: 416.00 [Kbytes/sec] received

Connection Times (ms)

min mean[+/-sd] median max

Connect: 3 7 2.5 9 9

Processing: 169 5054 2843.4 5061 9797

Waiting: 162 5037 2841.6 5051 9791

Total: 172 5062 2845.1 5070 9806

Percentage of the requests served within a certain time (ms)

50% 5070

66% 6742

75% 7472

80% 7983

90% 9082

95% 9549

98% 9742

99% 9760

100% 9806 (longest request)

On dev virtual machine

DutchCoding · March 6, 2012

Lifting the server siege... done.

Transactions: 701 hits

Availability: 100.00 %

Elapsed time: 24.75 secs

Data transferred: 3.86 MB

Response time: 7.62 secs

Transaction rate: 28.32 trans/sec

Throughput: 0.16 MB/sec

Concurrency: 215.80

Successful transactions: 701

Failed transactions: 0

Longest transaction: 20.50

Shortest transaction: 0.12

rkinfo · May 4, 2012

You all might want to start with Prestashop's own latest demonstration store.

Because if those can't pass the mustard then you guys are really shooting at nothing.

demo-store.prestashop.com/en/

http://www.webpagetest.org/result/120504_Y6_0f52d4a68690c35290020d9ccc46e6ef/1/performance_optimization/#first_byte_time

First Byte Time (back-end processing): 60/100

814 ms First Byte Time

423 ms Target First Byte Time

A featured store from the prestashop showcase

First Byte Time (back-end processing): 50/100

915 ms First Byte Time

420 ms Target First Byte Time

Another featured store from the prestashop showcase

First Byte Time (back-end processing): 6/100

1368 ms First Byte Time

432 ms Target First Byte Time

What do you expect to achieve with all these arbitrary numbers when the main one's still don't add up to anything?

kikbo · June 21, 2012

Yeah that is a bit worrisome...

navles · August 2, 2012

Hello everyone!

After a day of tweaking i finally managed to speed up my website!

The website runs on NGINX + Apache + APC.

Link : http://vps26008.publ...oudvps.com/ddv/ *Its a development environment!*

Well enough chit chat here are the results:

Note : In a few weeks i will offer cheap VPS's optimized for Prestashop!

Mike Schaap

[email protected]

Edited August 2, 2012 by navles (see edit history)

navles · August 2, 2012

Oh btw,

rkinfo @ webpagetest.org

I get the following results:

First Byte Time (back-end processing): 96/100

201ms First Byte Time

162ms Target First Byte Time

My server is located in Amsterdam and i used the checkpoint in Amsterdam to test my website.

infoseek · August 3, 2012

http://forge.prestashop.com/browse/PSCFI-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruno LEVEQUE updated PSCFI-5154:

---------------------------------

Status: Closed (was: Pending verification)

Hi Conny,

Thank you for your report.

We did a lot of optimization this week (price calculation, cart functions...etc.).

The v1.4.9 will definitely be faster than the v1.4.8.

Regarding the blocklayered module, we will do our best to optimize it before the release.

Regards

rkinfo · December 16, 2012

navles,

That's great man. nashtu3000 runs NGINX + Apache + APC, and has one of the fastest sites I've seen. Good to know that his homework paid off, right?

Oh btw,

rkinfo @ webpagetest.org

I get the following results:

First Byte Time (back-end processing): 96/100

201ms First Byte Time

162ms Target First Byte Time

My server is located in Amsterdam and i used the checkpoint in Amsterdam to test my website.

Page load time (time to first byte) and REQ/s

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites