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.

1. Lightning fast
page load time with
Spree & Ninefold

2. Hi. I’m Andrew.

7. How you measure
things makes a big
difference.

8. Why should you care
about performance?

9. 1. Do it for the users.

10. So, users, what do they
even want?

11. Google asked.

12. “We want more results.”

13. More results = 500ms slower.
20% drop in traffic and revenue.

14. Bad performance can ruin your UX.

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

17. 2. Do it for the money.

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/

21. What does good even
look like?

22. Google again.

23. “Mate! We’re much
quicker than that!”

24. Good.
Only problem is…

25. The mean is a lie.

26. Stats 101: the Bell Curve.

27. The real world.

28. What does that even mean?

29. Every 100ms matters.
How can hosting help?

30. Proof needs testing.

31. First:
find an app.

33. Why Spree?
- Ruby on Rails.
- Performance matters.
- Adoption through the roof.

34. Got the app:
what next?

35. 1. Set up a server.
2. Design a simulation.
3. Throw simulated users
at the server.
4. Measure the latency.

36. Tools.

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.

38. Capture click data.

39. JMeter.

40. JMeter.

41. JMeter.

42. Don’t cry.
There’s ruby-jmeter.

43. Our test plan.

44. Our test plan.

45. Running the test at scale.

46. Flood.io
- Requires some understanding of JMeter.
- Scales as big as you want to pay for.
- Gives high-level and very granular results.

47. Flood.io

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

49. Why Apdex?
95th/99th percentile is based on the mean.
We know the mean is a lie.
Apdex brings user experience to the table.

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

52. The results.

53. Smooth scaling.

54. Smooth pricing.

55. Consistent performance.

56. 1 in 20 clicks.

57. How many clicks is your
average user journey (to
checkout)?

58. Not 1 in 20 users.

59. What does this mean for
you?

60. 1. Every 100ms matters.
2. Consistency matters.

61. 1. Test, scale, test again.
2. Test your options.

62. Spree cached 2-2.

64. Performance,
engagement, sales.

65. Where should I host?

66. 1. Consistent performance.
Lowest cost of ownership.
Competitive VM pricing.
Lower sysadmin costs.
No PaaS premium.
With Ninefold of course…

67. 3. Smooth scaling costs.
Easy deployment & scaling.
Just enough control.
With Ninefold of course…

68. www.ninefold.com/spree
@ninefold
Schedule your individual demo
andrew.s@ninefold.com
@s4sharpie
Learn more.