gregors
Question y’all,
When I play with apache bench (ab) and I use the -k flag the output for the runs have this
Keep-Alive requests: 0
However if I try Cowboy for example it seems to report correctly
Keep-Alive requests: 15000
as well as being a bit faster (due to reused connections no doubt). I tried this with a few other languages, golang etc and they seemed to handled keep alives with ab.
Now I did an initial search through Bandit docs but I’m not seeing any settings pertaining to this. I did see a small blurb saying it was supported in http/1.1. Ok hmmmmmmmmmm.
What exactly is ab pushing out? Let’s spin up tcdump
sudo tcpdump -i any -A 'port 4000'
GET /health-check HTTP/1.0
Connection: Keep-Alive
Host: 127.0.0.1:4000
User-Agent: ApacheBench/2.3
Accept: */*
huh http/1.0 so I’m guessing Bandit just doesn’t support keep alives in that version. I don’t know exactly what the difference is, I should probably read the http spec at some point, but I am asking if there’s an easy way I can configure Bandit to support that. No problem if there isn’t an easy way. I’m just having fun. But it does look like other servers do support this…probably for ab use cases 
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
benwilson512
I realize this isn’t a direct answer to your question but Elixir folks have generally preferred to use wrk or wrk2 for HTTP benchmarking. It offers more options, stats, and as I recall handles your type of issue more consistently.
LostKobrakai
A quick google suggests keep-alive wasn’t officially supported before http 1.1, but was added as a response to people using it with http 1.0 without a spec for it existing. So it’s a question of how spec compliant bandit wants to be. A toggle might be a reasonable middleground.
gregors
Thanks, I am indeed aware of those. My larger point was the “doesn’t work with http/1.0” etc
gregors
yeah definitely looks like it wasn’t in the original spec.
I will say looking through some of the bandit source code, it’s really not bad reading at all! I might just mess with in on a branch etc. I have no idea how many people actually use http/1.0 in real life, probably not many…
gregors
Update after some weekend time to dig into this…
mtrudel
Thanks for the PR; it’s merged!
I’ll echo what others have said here; ab is in general a pretty outdated program that does a lot of oddball stuff like this (IIRC, this was actually strictly out of spec prior to the RFC911x series).