Katie Koschland - Ready, steady, crash - Codemotion Amsterdam 2019
•
0 likes•97 views
The key to finding the optimal solution to a problem is to threefold: maximise the number of tools in your ‘personal tool box’; know all their capabilities and uses; and to know which tool is best suited to fix the particular problem in front of you. This talk will enable you to grow all three aspects around load testing. It will look at what it means to ‘load test’ your application, how to get started with writing your first script and provide you with a case study and an insight as to the tools and techniques that we use here at the FT to help identify such performance issues.
Report
Share
Katie Koschland - Ready, steady, crash - Codemotion Amsterdam 2019
- 1. Ready, Steady, Crash! Katie Koschland Engineer, Financial Times @KKoschland
- 5. Could my users be having a similar experience? ¯_(ツ)_/¯ @KKoschland
- 7. I work at the
- 8. I am going to talk about my load testing journey. @KKoschland
- 9. I will aim to cover the core concepts behind load testing. @KKoschland
- 10. 1. The Challenge 2. Getting started 3. Identify performance issue 4. Troubleshooting 5. Outcomes @KKoschland
- 12. @KKoschland
- 13. Testing the technical limits of our node application. @KKoschland
- 15. Will our application crash? @KKoschland
- 16. If so, can our application recover? @KKoschland
- 17. What happens to the user experience? @KKoschland
- 18. @KKoschland
- 19. I was told the answers could be found by load testing. @KKoschland
- 20. So, what exactly is load testing ? @KKoschland
- 21. @KKoschland “It is about simulating ordinary user activity and then applying stress until it reaches failure.” @Jadware
- 22. How can I apply this so called ‘stress’ to my application? @KKoschland
- 24. There are many frameworks out there. @KKoschland
- 25. @KKoschland
- 26. I decided to go with Artillery. @KKoschland
- 28. @KKoschland
- 29. Allows you to customise JS code within your scripts. @KKoschland
- 30. @KKoschland
- 31. Scripts could be configured using YAML. @KKoschland
- 32. @KKoschland
- 35. Decide on the type of requests. @KKoschland
- 36. Scripts need to be able to represent ordinary user activity. @KKoschland
- 37. @KKoschland
- 38. Decide on the shape of load. @KKoschland
- 39. @KKoschland
- 40. You may already know the shape of load. @KKoschland
- 41. Before the release of a push notification. @KKoschland
- 42. @KKoschland
- 43. But it’s also okay if you don’t know... @KKoschland
- 44. You can split the script into four separate phases. @KKoschland
- 45. Warm Up Arrival rate of 10 virtual users/second for 60 seconds. @KKoschland
- 46. Ramp up Arrival rate of 10 to 25 new virtual users/second for 120 seconds. @KKoschland
- 47. Cruise Arrival rate of 25 virtual users/second for 1200 seconds. @KKoschland
- 48. Crash Arrival rate of 100 virtual users/second for 30 seconds. @KKoschland
- 49. @KKoschland
- 50. @KKoschland Shape of load hitting FT.com homepage warm up ramp up Cruise Crash
- 51. 1. The challenge 2. Getting started 3. Identify performance issue 4. Troubleshooting 5. Outcomes @KKoschland
- 52. What should the first script look like? @KKoschland
- 53. The script is split into two sections. @KKoschland
- 55. @KKoschland
- 56. @KKoschland
- 57. @KKoschland
- 58. @KKoschland
- 60. @KKoschland
- 61. @KKoschland
- 62. @KKoschland
- 64. @KKoschland
- 66. Artillery will provide you with a summary report which contains detailed metrics. @KKoschland
- 67. @KKoschland
- 68. @KKoschland
- 69. @KKoschland
- 70. @KKoschland
- 71. @KKoschland
- 72. @KKoschland
- 73. 1. The Challenge 2. Getting started 3. Identify performance issue 4. Troubleshooting 5. Outcomes @KKoschland
- 74. @KKoschland
- 76. 1. The Challenge 2. Getting started 3. Identify performance issue 4. Troubleshooting 5. Outcomes @KKoschland
- 77. How do we find the culprit? @KKoschland
- 78. @KKoschland
- 79. @KKoschland
- 82. @KKoschland
- 83. @KKoschland
- 85. @KKoschland
- 86. @KKoschland
- 87. Increased the pool size, decreased the retry timeout. @KKoschland
- 88. Parameterized the cypher query @KKoschland
- 90. @KKoschland
- 91. @KKoschland
- 92. @KKoschland
- 93. @KKoschland
- 95. @KKoschland
- 96. @KKoschland
- 97. So, what was the fix? @KKoschland
- 98. @KKoschland
- 99. So, why have I shared this example with you? @KKoschland
- 101. 1. The Challenge 2. Getting started 3. Identify performance issue 4. Troubleshooting 5. Outcomes @KKoschland
- 102. Outcomes @KKoschland
- 103. Able to measure, assess and improve the overall performance of our application. @KKoschland
- 104. Able to assess the reliability of our application. @KKoschland
- 105. To fully understand the performance and reliability of what you’re building, you should all be load testing your application. @KKoschland
- 106. Thanks @KKoschland