Our relationship started when Ninefold chose Spree as the App to performance test our platform. We chose Spree because for Spree apps every millisecond matters. As a part of the trip, I presented at Spree inaugural webinar series on why performance matters for your Spree app and how hosting can help.
This is just the start of exciting work we are doing together. We discussed how Ninefold and Spree can bring better performance to Spree stores: Spree on the technology and Hub side, Ninefold from hosting.
15. Improved load time by 400ms.
Increased traffic by 9%.
http://www.slideshare.net/stoyan/yslow-20-presentation
16. Visitors experiencing the best 10% of load
times viewed 3 times more pages than
those getting the worst 10%.
http://assets.en.oreilly.com/1/event/29/The%20Secret%20Weapons%20of%20the%20AOL%20Optimization%20Team%20Presentation.pdf
18. For every 100ms of load time
improvement:
Sales increased by 1%.
https://sites.google.com/site/glinden/Home/StanfordDataMining.2006-11-28.ppt?attredirects=0
19. Load time: 6 seconds -> 1.2 seconds.
Page views: up 25%.
Revenue: up 12%.
http://www.slideshare.net/timmorrow/shopzilla-performance-by-design-2433735
20. 47% of ecommerce consumers expect a
page load of 2 seconds or less.
40% abandonment rate on pages that take
more than 3 seconds to load.
http://blog.kissmetrics.com/loading-time/
37. Our tool chain.
Chrome
-> Developer tools provide data for the test plan.
ruby-jmeter
-> Provides ruby-based testing DSL.
-> Generates JMeter XML.
Flood.io
-> Eats JMeter XML.
-> Spin up a “Grid” of users following the XML-defined script.
-> Measures and reports response times.
48. Apdex.
t = acceptable response time
satisfied = response time < t
tolerating = t < response time < 4t
frustrated = response time > 4t
Apdex [t] = (satisfied + (tolerating/2))/total requests
50. Happiness as a constant.
Apdex [0.75] 0.95
Benchmarked against Heroku.
Higher threshold than we would have
liked.
51. Test parameters.
• Choose 5 configurations that range from $100 per
month to $1,000 per month.
• Run flood.io tests using a 60 second ramp up and a
300 second test duration.
• Vary the concurrent user count to discover the
maximum number of users that can be serviced while
maintaining an Apdex [0.75] 0.95