10.6k GitHub stars and counting — hatoo/oha is a Rust project TopGit is tracking across repositories on the platform. Ohayou(おはよう), HTTP load generator, inspired by rakyll/hey with tui animation.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
You can enable VSOCK support by enabling vsock feature.
cargo install --features vsock oha
You can enable experimental HTTP3 support by enabling the http3 feature. This uses the H3 library by the developers of Hyper.
It will remain experimental as long as H3 is experimental. It currently depends on using rustls for TLS.
Download pre-built binary
You can download pre-built binary from Release page for each version and from Publish workflow and Publish PGO workflow for each commit.
You can also build and create a container image including oha
docker build -t hatoo/oha:latest .
Then you can use oha directly through the container
docker run --rm -it --network=host hatoo/oha:latest https://example.com:3000
Profile-Guided Optimization (PGO)
You can build oha with PGO by using the following commands:
bun run pgo.js
And the binary will be available at target/[target-triple]/pgo/oha.
Note: Please keep in mind that in order to run the aforementioned command,
you need to have installed cargo-pgo cargo package.
You can install it via cargo install cargo-pgo.
Platform
Linux - Tested on Ubuntu 18.04 gnome-terminal
Windows 10 - Tested on Windows Powershell
MacOS - Tested on iTerm2
Usage
-q option works different from rakyll/hey. It's set overall query per second instead of for each workers.
Ohayou(おはよう), HTTP load generator, inspired by rakyll/hey with tui animation.
Usage: oha [OPTIONS] <URL>
Arguments:
<URL> Target URL or file with multiple URLs.
Options:
-n <N_REQUESTS>
Number of requests to run. Accepts plain numbers or suffixes: k = 1,000, m = 1,000,000 (e.g. 10k, 1m). [default: 200]
-c <N_CONNECTIONS>
Number of connections to run concurrently. You may should increase limit to number of open files for larger `-c`. [default: 50]
-p <N_HTTP2_PARALLEL>
Number of parallel requests to send on HTTP/2. `oha` will run c * p concurrent workers in total. [default: 1]
-z <DURATION>
Duration of application to send requests.
On HTTP/1, When the duration is reached, ongoing requests are aborted and counted as "aborted due to deadline"
You can change this behavior with `-w` option.
Currently, on HTTP/2, When the duration is reached, ongoing requests are waited. `-w` option is ignored.
Examples: -z 10s -z 3m.
-w, --wait-ongoing-requests-after-deadline
When the duration is reached, ongoing requests are waited
-q <QUERY_PER_SECOND>
Rate limit for all, in queries per second (QPS)
--burst-delay <BURST_DURATION>
Introduce delay between a predefined number of requests.
Note: If qps is specified, burst will be ignored
--burst-rate <BURST_REQUESTS>
Rates of requests for burst. Default is 1
Note: If qps is specified, burst will be ignored
--rand-regex-url
Generate URL by rand_regex crate but dot is disabled for each query e.g. http://127.0.0.1/[a-z][a-z][0-9]. Currently dynamic scheme, host and port with keep-alive do not work well. See https://docs.rs/rand_regex/latest/rand_regex/struct.Regex.html for details of syntax.
--urls-from-file
Read the URLs to query from a file
--max-repeat <MAX_REPEAT>
A parameter for the '--rand-regex-url'. The max_repeat parameter gives the maximum extra repeat counts the x*, x+ and x{n,} operators will become. [default: 4]
--dump-urls <DUMP_URLS>
Dump target Urls <DUMP_URLS> times to debug --rand-regex-url
--latency-correction
Correct latency to avoid coordinated omission problem. It's ignored if neither -q nor --burst-delay is set.
--no-tui
No realtime tui
--fps <FPS>
Frame per second for tui. [default: 16]
-m, --method <METHOD>
HTTP method [default: GET]
-H <HEADERS>
Custom HTTP header. Examples: -H "foo: bar"
--proxy-header <PROXY_HEADERS>
Custom Proxy HTTP header. Examples: --proxy-header "foo: bar"
-t <TIMEOUT>
Timeout for each request. Default to infinite.
--connect-timeout <CONNECT_TIMEOUT>
Timeout for establishing a new connection. Default to 5s. [default: 5s]
-A <ACCEPT_HEADER>
HTTP Accept Header.
-d <BODY_STRING>
HTTP request body.
-D <BODY_PATH>
HTTP request body from file.
-Z <BODY_PATH_LINES>
HTTP request body from file line by line.
-F, --form <FORM>
Specify HTTP multipart POST data (curl compatible). Examples: -F 'name=value' -F 'file=@path/to/file'
-T <CONTENT_TYPE>
Content-Type.
-a <BASIC_AUTH>
Basic authentication (username:password), or AWS credentials (access_key:secret_key)
--aws-session <AWS_SESSION>
AWS session token
--aws-sigv4 <AWS_SIGV4>
AWS SigV4 signing params (format: aws:amz:region:service)
-x <PROXY>
HTTP proxy
--proxy-http-version <PROXY_HTTP_VERSION>
HTTP version to connect to proxy. Available values 0.9, 1.0, 1.1, 2.
--proxy-http2
Use HTTP/2 to connect to proxy. Shorthand for --proxy-http-version=2
--http-version <HTTP_VERSION>
HTTP version. Available values 0.9, 1.0, 1.1, 2, 3
--http2
Use HTTP/2. Shorthand for --http-version=2
--host <HOST>
HTTP Host header
--disable-compression
Disable compression.
-r, --redirect <REDIRECT>
Limit for number of Redirect. Set 0 for no redirection. Redirection isn't supported for HTTP/2. [default: 0]
--disable-keepalive
Disable keep-alive, prevents re-use of TCP connections between different HTTP requests. This isn't supported for HTTP/2.
--no-pre-lookup
*Not* perform a DNS lookup at beginning to cache it
--ipv6
Lookup only ipv6.
--ipv4
Lookup only ipv4.
--cacert <CACERT>
(TLS) Use the specified certificate file to verify the peer. Native certificate store is used even if this argument is specified.
--cert <CERT>
(TLS) Use the specified client certificate file. --key must be also specified
--key <KEY>
(TLS) Use the specified client key file. --cert must be also specified
--insecure
Accept invalid certs.
--connect-to <CONNECT_TO>
Override DNS resolution and default port numbers with strings like 'example.org:443:localhost:8443'
Note: if used several times for the same host:port:target_host:target_port, a random choice is made
--no-color
Disable the color scheme. [env: NO_COLOR=]
--unix-socket <UNIX_SOCKET>
Connect to a unix socket instead of the domain in the URL. Only for non-HTTPS URLs.
--stats-success-breakdown
Include a response status code successful or not successful breakdown for the time histogram and distribution statistics
--db-url <DB_URL>
Write succeeded requests to sqlite database url E.G test.db
--debug
Perform a single request and dump the request and response
-o, --output <OUTPUT>
Output file to write the results to. If not specified, results are written to stdout.
--output-format <OUTPUT_FORMAT>
Output format [default: text] [possible values: text, json, csv, quiet]
-u, --time-unit <TIME_UNIT>
Time unit to be used. If not specified, the time unit is determined automatically. This option affects only text format. [possible values: ns, us, ms, s, m, h]
--worker-threads <WORKER_THREADS>
Number of native OS threads used by the async runtime (tokio).
Takes precedence over the TOKIO_WORKER_THREADS environment variable. When neither is set, the number of physical CPU cores is used.
-h, --help
Print help
-V, --version
Print version
Performance
oha uses faster implementation when --no-tui option is set and both -q and --burst-delay are not set because it can avoid overhead to gather data realtime.
Output
By default oha outputs a text summary of the results.
oha prints JSON summary output when --output-format json option is set.
The schema of JSON output is defined in schema.json.
When --output-format csv is used result of each request is printed as a line of comma separated values.
Tips
Stress test in more realistic condition
oha uses default options inherited from rakyll/hey but you may need to change options to stress test in more realistic condition.
I suggest to run oha with following options.
oha <-z or -n> -c <number of concurrent connections> -q <query per seconds> --latency-correction --disable-keepalive <target-address>
--disable-keepalive
In real, user doesn't query same URL using Keep-Alive. You may want to run without Keep-Alive.
--latency-correction
You can avoid Coordinated Omission Problem by using --latency-correction.
With -q (or --burst-delay), oha schedules requests at a fixed rate, but a request can only be sent when one of the -c connections is free. If the server is slow, scheduled requests wait for a connection.
By default, latency is measured from when a request is actually sent, so this waiting time is left out and the results look better than what clients sending at that rate would see.
With --latency-correction, latency is measured from the time the request was scheduled, so the waiting time is included.
It has no effect unless -q or --burst-delay is set.
Burst feature
You can use --burst-delay along with --burst-rate option to introduce delay between a defined number of requests.
oha -n 10 --burst-delay 2s --burst-rate 4
In this particular scenario, every 2 seconds, 4 requests will be processed, and after 6s the total of 10 requests will be processed.
NOTE: If you don't set --burst-rate option, the amount is default to 1
Dynamic url feature
You can use --rand-regex-url option to generate random url for each connection.
Each Urls are generated by rand_regex crate but regex's dot is disabled since it's not useful for this purpose and it's very inconvenient if url's dots are interpreted as regex's dot.
Optionally you can set --max-repeat option to limit max repeat count for each regex. e.g http://127.0.0.1/[a-z]* with --max-repeat 4 will generate url like http://127.0.0.1/[a-z]{0,4}
Currently dynamic scheme, host and port with keep-alive are not works well.
URLs from file feature
You can use --urls-from-file to read the target URLs from a file. Each line of this file needs to contain one valid URL as in the example below.
How does hatoo/oha compare to other Mobile projects?
hatoo/oha is tracked by TopGit in the Mobile category, with 10.6k GitHub stars and written in Rust. Browse the Mobile topic page on TopGit to compare it against similar projects by stars and activity.
Is hatoo/oha open source?
Yes — hatoo/oha ships under the MIT license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/hatoo/oha.
What else is in the Mobile space?
hatoo/oha is tracked by TopGit under the Mobile category, alongside 9 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What is hatoo/oha?
hatoo/oha (hatoo/oha) is a Rust project on GitHub. From the project's own README: Ohayou(おはよう), HTTP load generator, inspired by rakyll/hey with tui animation.
Where do I read more about hatoo/oha?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/hatoo/oha is the definitive source.
Why is hatoo/oha categorized under Mobile?
TopGit places hatoo/oha in the Mobile category based on its GitHub topics and description (tagged: "benchmark", "cli", "command-line"). Categories are assigned from real repository metadata, not editorial guesswork.
Read full README in the tab above.
Want a second opinion on oha?
Ask an AI that can read this page — one click and you get its take on oha.
/oha
