Uploaded byQA or the Highway
Leandro Melendez - Chihuahua Load Tests.pdf
- The document discusses using small "Chihuahua-sized" load tests versus large "Big Ass Load Tests (BALT)" and argues that smaller load tests are better for continuous integration pipelines. - Chihuahua-sized load tests are described as small, lightweight, manageable, and easy to include in pipelines without disrupting environments or requiring many resources. - In contrast, BALTs are characterized as heavy, disruptive, resource-intensive, and only suitable when needed outside of pipelines. The document recommends focusing on small, lean, and friendly load tests that can be run continuously.
More Related Content
Similar to Leandro Melendez - Chihuahua Load Tests.pdf
Leandro Melendez - Chihuahua Load Tests.pdf
- 1.
- 2. Whoami? qLeandro Melendez qAdvocate @Grafanak6 qSeñor Performo @srperf qPerfBytes qYoutube qBook
- 3.
- 4. Summmmmary vPerf and puppies vLargeVs Small vChihuahua Tips
- 5.
- 6. Other pups You mayremember me from such… https://www.srperf.com/functional-vs-performance-test-cases/
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16. What do Ireally Mean BALT Chihuahua
- 17.
- 18.
- 19.
- 20.
- 21.
- 22. Drags everything Environments, processes,pipelines, etc.
- 23.
- 24.
- 25. Tiny and light Wontkill anyone Manageable . . . . . .. . . Unnoticeable .. . . . . .. . . Small SW too!
- 26. Work well Focused, straight,show ROI
- 27. Fast n Snappy Don’tneed many resources Happy Tiny length Repeatable Stable Small loads
- 28.
- 29.
- 30. Avoid weird ones Heavywhen you want load
- 31.
- 32. Load! Can be puttogether!
- 33. Serious talk Huge loadtests (BALT) • Heavy • Disruptive • Weird in elastic envs • Questionable in most cases • Results don’t last long • Code/Env freeze • Need special ppl/resources • Hard to integrate agile • Increase cloud costs • Only when needed Mini load tests (Chihuahua) • Light n lean • Hardly noticeable • Pulse of the solution • Continuous and pipelines • Results update frequently • Run them everywhere no freeze • Easy for whole team • Agile create, update, run • No impact • Always, on every environment
- 34. Subset of cloudload tests Number of runs Duration (mins)
- 35.
- 36. Stop the obsession - Youlive in an apartment - It is tiny and moving - Lots of people in, moving - Huge food and 💩 - Time requirements - Could kill envs
- 37. Smaller Is better - Chihuahuafirst - Little resources - Wont kill anyone - Purseable (pipelines) - Can play inside (prod) - Shareable n’friendly
- 38.
- 39.
- 40. sniff everything Tiny &continuously outside the pipeline
- 41. Keep smells For futureuse, comparisons & observability
- 42. Don’t have tosniff everything Small load for what is in the release
- 43. Avoid huge inpipelines Slow, Heavy, Risky, impactful, etc.
- 44. Don’t stop thepipeline Slow, Heavy, Risky, impactful, etc.
- 45. need No huge .. .almost Chihuahua is enough Rarely Need Huge Huge So 2000’s
- 46. Light Keep lean: runs,sw, reqs.
- 47. Friendly loads-scripts Accessible tothe whole team
- 48. When you need BALT Youmay meet Taylor Swift
- 49. When you need BALT Youhave many chihuahuas, stack them … but not in the pipeline
- 50. Gotta go! But thereis much more…
- 51.
- 52. Q&A @SrPerf FB TWYT Leandro Melendez LI