Hacker GitHub

← All repos

giltene/wrk2

View on GitHub ↗ ★ 4,639 C

A constant throughput, correct latency recording variant of wrk

23 mentions on Hacker News by 21 people: 4 stories, 19 comments · first 2014-11-11 · latest 2025-11-21

Mentions per year 23 mentions · busiest year 2015 (5)
20082026
  1. 10 years old and still relevant. Gil created a wrk fork https://github.com/giltene/wrk2 to handle coordinated omission better. I used using his fork for many years. But I think he stopped updating it after a while. Good load testing tools…
    comment by rdtsc · 2025-11-21 · in Measuring Latency (2015)
  2. …is notable problem with wrk called "coordinated omission": https://github.com/wg/wrk/issues/485 https://github.com/giltene/wrk2 https://news.ycombinator.com/item?id=34148502 Benchmarking is difficult. And there is lot of subtlety on how…
    comment by zokier · 2024-05-16 · in Swift sucks at web serving or does it?
  3. …but wrk2 improves on it (and on wrk version 1) in multiple ways, so that's what I use myself. [1] https://github.com/giltene/wrk2 [2] https://httpd.apache.org/docs/2.2/programs/ab.html
  4. …I'd use or borrow some techniques from wrk2 that makes sure to account for coordinated omission. https://github.com/giltene/wrk2 https://github.com/fede1024/kafka-benchmark https://github.com/fede1024/rust-rdkafka
  5. Note that Gil Tene has his own wrk fork. The readme has some interesting notes about wrk: https://github.com/giltene/wrk2 There is also open issue on GH questioning wrks approach for resolving coordinated omission:…
  6. …the talks from Gil Tene. I always reach for his fork of wrk whenever I need to test throughput: https://github.com/giltene/wrk2
    comment by leetrout · 2022-12-29 · in How Not to Measure Latency (2015)
  7. i use https://github.com/giltene/wrk2 pretty regularly. it has decent lua hooks to customize behavior but i use it in the dumbest way possible to hammer a server at a fixed rate with the same payload over and over. i run it by hand after a…
  8. …optimizations or have specific behaviors that aren't actually useful in a production context. [0] https://github.com/giltene/wrk2
    comment by dralley · 2022-04-17 · in Is Rust Web Yet?
  9. I'm not disagreeing with your results, but you should be using https://github.com/giltene/wrk2 based benchmarks to avoid coordinated omission errors in measuring latency.
    comment by sa1 · 2021-06-30 · in An Elixir adoption success story
  10. Did you consider wrk2? https://github.com/giltene/wrk2 Maybe you duplicated some of these fixes?
    comment by diroussel · 2021-05-20 · in Extreme HTTP Performance Tuning
  11. > I know there's much better ways of testing load/performance. such as https://github.com/giltene/wrk2
    comment by sumnulu · 2020-03-23 · in A Starter Kit for Emergency Websites
  12. https://github.com/giltene/wrk2
  13. wrk2: https://github.com/giltene/wrk2
  14. And wrk2 ( https://github.com/giltene/wrk2 ) is the way to measure it.
  15. For very high traffic loads, I have yet to find anything that compares to wrk ( https://github.com/giltene/wrk2 ). IME, it scales better and more efficiently than anything else I've tried, short of complex distributed tools that are only…
  16. …[2] http://jmeter.512774.n5.nabble.com/Coordinated-Omission-CO-p... [3] https://github.com/giltene/wrk2
    comment by meteorfox · 2015-11-01 · in How Not to Measure Latency [pdf]
  17. …99th-percentile worst experience will experience about 100s of latency, not 2s! E.g. the author's https://github.com/giltene/wrk2 tries to avoid this "coordinated omission" problem by sending requests at a constant rate, instead of…
    comment by JoachimSchipper · 2015-11-01 · in How Not to Measure Latency [pdf]
  18. …scripting for request generation, response processing and reporting. There is another fork of it ( https://github.com/giltene/wrk2 ) which can be used if you want test at a consistent RPS.
  19. …wrk for the coordinated omission problem, which he explains in the readme of that same repo[1]. [1] https://github.com/giltene/wrk2