- Author: [[Rafaela Azevedo]] - Full Title: Load Tests: Jmeter vs K6 – Rafaela Azevedo - Tags:: [[JMeter Competitive Disadvantages]] [[k6 (tool)]] [[JMeter]] - URL: https://azevedorafaela.com/2020/07/06/load-tests-jmeter-vs-k6/ ### Highlights first synced by [[Readwise]] [[2020-12-10]] > __Jmeter is a great and powerful tool, but depending on what you really need (something more lighter) then Jmeter might become an over complex, slow, hard to maintain tool.__ - [[Rafaela Azevedo]] > - Supports ramp-up phases and flexible load > - Plugins available to be able to configure flexible load - "You need a plugin for everything" > - Resources Consumption Heavy to run tests with multiple users on a single machine, more memory consumption Lightweight and doesn’t take up so much memory of your machine - JMeter -  - > Easy to use with Version Control Systems No Yes - Add listeners, but consume more memory - > Number of Concurrent Users: Thousands, under restrictions -- [[Rafaela Azevedo]] - Jmeter is most used when: - > JMeter is most used when: You need to perform a complex load including different protocols ^466415 - [[Rafaela Azevedo]] - You can record scenarios - Robust support and training ecosystem - Require that a full scenario be written for every test - If you need to simulate specific load with some custom ramp-up patterns - If you just prefer UI desktop app for scripts creation, or you just do not know Javascript/YAML/JSON well enough   - K6 solves some specific problems: - CLI tool with developer-friendly APIs. - You can use HAR files to generate record sessions - > Checks and Thresholds – for goal-oriented, automation-friendly load testing - [[Rafaela Azevedo]] [[K6 OSS Competitive Advantages]] - Open source, great support and documentation - > Lightweight uses Javascript - "Lightweight" - "Javascript as a scripting language" - Does not run in NodeJS and doesn’t run in a browser