Your SlideShare is downloading. ×
Bargento 1.0 – NBS System – Menos de 1 segundo para cargar Magento
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Bargento 1.0 – NBS System – Menos de 1 segundo para cargar Magento

1,106
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,106
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Less Than 1 Second to Load Emile Heitor – NBS System
  • 2. Why Care ? A word from our friends at the W3C : From http://www.w3.org/Protocols/NL-PerfNote.html 0.1 second (one tenth of a second). Ideal response time. The user doesn't sense any interruption. 1 second. Highest acceptable response time. Download times above 1 second interrupt the user experience. 10 seconds. Unacceptable response time. The user experience is interrupted and the user is likely to leave the site or system.
  • 3. Why Care ?
  • 4. “The Magento Problem” 1/2 Awesome looking product Freedom and flexibility Probably the best E-Commerce platform around Open Source: Widely known, recognized and supported Huge userbase, massive community, impressive number of 3rd party modules
  • 5. “The Magento Problem” 2/2 Flexibility has a price Large amount of PHP code to be interpreted Object Oriented programming: CPU intensive “Clean code” does not always mean “fast rendering” Many objects to be handled (Javascript, CSS, lots of media), all bound by PHP 3rd party modules often slower than core itself
  • 6. Everybody Loves Benchmarks 1/3 The benchmark was completed using the following hardware Double Intel Xeon 5550 @ 2.70GHz (8 cores total) 4GB DDR3 RAID1 143GB SAS 10k RPM disks Pretty good hardware, average configuration nowadays.
  • 7. Everybody Loves Benchmarks 2/3 The benchmark was completed using the following main softwares on the target Web Server  Debian Stable 64 Bits  Apache 2.2  PHP 5  MySQL 5  Magento 1.4.0.1 (yes, we like it on the edge)  Demo Store
  • 8. Everybody Loves Benchmarks 3/3 The benchmark was completed using the following main softwares on the bench-machine Debian Stable 64 Bits Python 2.6 Funkload SVN (as I said, on the edge) URL used: Magento Demostore Homepage
  • 9. Worst Case Scenario No Magento Cache, no tuning, direct access Max 13s
  • 10. Magento Cache Performance Magento Cache, no tuning, direct access Max 4.1s
  • 11. APC Magic Magento Cache, full tuning, direct access, APC Max 0.9s
  • 12. NANDs are faster  Magento Cache, full tuning, direct access, APC, tmpfs Max 0.75s
  • 13. Typical NBS Ecosystem
  • 14. Single NGINX Reverse Proxy Magento Cache, full tuning, APC, tmpfs, NGINX Max 0.54s
  • 15. NGINX Reverse Proxy + Page Cache Magento Cache, full tuning, APC, tmpfs, NGINX Max 0.22s
  • 16. More numbers 1/2 Bench configuration Cycles of concurrent users: [5, 15, 25, 50, 75, 100] Cycle duration: 30s Sleeptime between request: 0s Startup delay between thread: 0.01s
  • 17. More numbers 2/2 Bench content 1 complete page (Homepage) 4 link 12 image Maximum of 3558 tests Maximum of 3776 pages Maximum of 62467 requests A total of 62k requests in 3 minutes
  • 18. More to come Magento environment tuning whitebook Nitrogento extension Full benchmarks available online Other UNIX platforms ? Ongoing R&D on NGINX as a Web Server... spoiler ?
  • 19. Someone's gonna be mad at me  Direct access, APC, tmpfs, NGINX Web Server + PHP-FPM Max 0.61s