redis-benchmarks-specification
locust
| redis-benchmarks-specification | locust | |
|---|---|---|
| 1 | 58 | |
| 26 | 23,647 | |
| - | 0.8% | |
| 4.7 | 9.8 | |
| 28 days ago | 6 days ago | |
| Python | Python | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
redis-benchmarks-specification
-
Redis 7 benchmarks 3-26% slower than 6
- Optimized GEO commands ( GEODIST, GEOSEARCH BYBOX and BYRADIOUS ) leading to up to 5.4x more ops/sec and still drop in latency of up to 6.4X in the p50 latency.
You can check the redis repo PRs that affect performance easily via: https://github.com/redis/redis/pulls?q=is%3Apr+label%3Aactio...
Taking this opportunity to also remind that our goal (Redis Performance Teams) is to make Redis Performance open and free of bias in any manner. Anyone can contribute in https://github.com/redis/redis-benchmarks-specification either by asking for specific use-cases to be benchmarked, sharing how they're using Redis so we can map that to new benchmarks, and as always submitting PRs to redis itself.
locust
- Protegendo APIs da Esquerda para a Direita (e em td no meio do caminho) [Tradução +/- Comentada]
-
codecov gone from PyPi
I'm assuming this breaks a ton more than just my project (https://github.com/locustio/locust/actions/runs/4687344723/jobs/8315803536)
-
Simple, open-source, lightweight stress tool
If, like me, AGPL isn't your cup of tea, you can look at vegeta or locust which are both MIT.
- What server to pick for a good amount of consistent traffic?
-
Load/Stress test Apache
locust if you can code
- Simple web performance testing with Selenium?
- Can I use pytest for smoke testing?
-
Load Testing: An Unorthodox Guide
Agreed with a lot of the points here, like starting small with a single piece of your API, then slowly expanding your tests once you’re comfortable that you know what you’re doing.
Note that if you use the Locust framework to write your load tests in Python, it takes care of measuring and reporting the latency and throughput for you. It’s really nice.
https://locust.io/
-
CloudRun min max
For my application, to tune these parameters I used a load testing tool. I built a script using Locust.
- I wrote a kubernetes operator for “locust”, should I open source it
What are some alternatives?
python-kv-benchmark - Benchmarks for performing common operations with python client libraries for Memcached, Redis, Redis Cluster, Dragonfly, MongoDB & Etcd
Selenium WebDriver - A browser automation framework and ecosystem.
Redis - Redis is an in-memory database that persists on disk. The data model is key-value, but many different kind of values are supported: Strings, Lists, Sets, Sorted Sets, Hashes, Streams, HyperLogLogs, Bitmaps.
PyAutoGUI - A cross-platform GUI automation Python module for human beings. Used to programmatically control the mouse & keyboard.
locust-grasshopper - a load testing tool extended from locust
Gatling - Modern Load Testing as Code
aiounittest - Test python asyncio-based code with ease.
splinter - splinter - python test framework for web applications
siege - Siege is an http load tester and benchmarking utility
PyRestTest - Python Rest Testing
ddosify - Effortless Kubernetes Monitoring and Performance Testing. Available on CLI, Self-Hosted, and Cloud
Selenium Wire - Extends Selenium's Python bindings to give you the ability to inspect requests made by the browser.