This release is a pre-release and may not be stable for production use.
httpperf
An asyncio HTTP client for load testing, built on libcurl.
Design
A load-testing client has three jobs: drive as much load as possible from each machine, report the server's response times rather than time spent waiting on the client, and read responses promptly so the server never sees a slow reader. httpperf is built around these.
All network I/O runs in a small C event loop (the vendored ae reactor from Redis) on its own thread, which never takes the GIL. Python hands requests to that thread and collects finished responses through pipes:
asyncio loop ──req_in pipe──▶ curl thread (ae + curl multi) ──▶ sockets
▲ │
└──────── req_out pipe ◀────────┘
Bytes are read off the wire as they arrive, whatever Python is doing. If Python falls behind, finished responses wait in the pipe rather than in socket buffers, so the client simply sends new requests more slowly, and curl's timings stay accurate. The cost is the hand-off itself, and the curl thread uses roughly one extra core under load. That is deliberate: a spare core is cheap, and response times you can't trust are worthless.
Response.client_lag shows how far Python is behind (see Timings).
Install
pip install httpperf
Wheels are published for Linux on x86_64 and aarch64, for Python 3.9 to 3.15, with glibc 2.34 or later (Ubuntu 22.04, Debian 12, RHEL 9 and later) or musl (Alpine). They include their own libcurl, with HTTP/2 and HTTP/3.
Anywhere else, including Python 3.8, pip builds from source against the system's libcurl, which needs its development headers and a C compiler. That libcurl decides whether HTTP/3 is available: curl -V lists HTTP3 under Features when it does.
sudo apt install libcurl4-openssl-dev # Debian/Ubuntu
pip install httpperf
To build against your own libcurl even where a wheel exists, skip the wheel, point the build at it and make sure it is found at run time:
CFLAGS=-I$PREFIX/include LDFLAGS="-L$PREFIX/lib -Wl,-rpath,$PREFIX/lib" pip install --no-binary httpperf httpperf
A session with http_version="HTTP/3" raises ValueError if the libcurl in use lacks HTTP/3.
Quick start
import asyncio
import httpperf
async def main():
async with httpperf.Session() as session:
r = await session.get("https://example.com/")
print(r.status_code, r.http_version, r.total_time, r.client_lag)
asyncio.run(main())
Sessions are cheap: create one per virtual user or journey. They share a default Engine (the curl thread, the shared connection pool and the TLS cache) unless you pass your own.
API
Session(*, engine=None, ...)
All arguments are keyword-only. A session can be created anywhere, even outside a running asyncio loop.
| Argument | Default | Meaning |
|---|---|---|
engine |
None |
The Engine to use. None means the default engine of the asyncio loop the session is first used in, created when first needed and shared by every session in that loop without one. |
connections |
"shared" |
"shared": the engine's pool. "session": the session's own pool. "none": a new connection for every request. |
tls |
"shared" |
Where TLS session tickets are kept. "shared": in the engine, so new connections resume their handshake. "session": per session, so each session starts with a full handshake. |
http_version |
"HTTP/2" |
"HTTP/2": HTTP/2 over TLS when the server offers it, with requests waiting to share one multiplexed connection. Plain http uses HTTP/1.1. "HTTP/1.1": HTTP/1.1 only. "HTTP/3": HTTP/3 over QUIC only, with no fallback, so requests fail if the server does not offer it. |
idle_timeout |
118 |
Seconds a connection may sit idle and still be reused. |
max_connection_age |
0 |
Seconds after which a connection is no longer reused, however busy it is. 0 means no limit. |
max_host_connections |
0 |
Per-session cap on connections per host. Needs connections="session" or "none". |
max_connections |
0 |
Per-session cap on connections in use. Needs connections="session" or "none". |
cert |
None |
(certfile, keyfile) paths for a client certificate, used by every request unless the request overrides it. |
timeout |
None |
Seconds allowed for each request, from the start of the transfer to the last byte (each redirect hop separately). None or 0 means no limit. Prefer this to asyncio.wait_for or cancelling the task: a cancelled request still runs to the end in curl and holds its connection until then, while a timeout stops it. |
connect_timeout |
None |
Seconds allowed to connect, TLS included. None means curl's default of 300 s. |
verify |
False |
Server certificate checking. False: none, as most load tests want. True: check against the system CA bundle: SSL_CERT_FILE if set, otherwise libcurl's own default, or the usual system locations if it has none. A path: check against that CA bundle. Requests can override it. |
json_dumps |
None |
Function that turns a json= argument into the request body (str or bytes). None means the engine's. |
json_loads |
None |
Function that turns the response body (bytes) into the result of json(). None means the engine's. |
Proxies come from the environment, as curl reads them: http_proxy (not HTTP_PROXY, which curl ignores for security), https_proxy or HTTPS_PROXY, then all_proxy or ALL_PROXY, with no_proxy or NO_PROXY for exceptions. A session reads them once, when it is created, so later changes apply to new sessions only.
Cookies always belong to the session, whatever the connection settings.
Engine(*, max_host_connections=0, max_total_connections=0, max_idle_connections=1000, json_dumps=..., json_loads=...)
What sessions share: the curl thread, the shared connection pool, the TLS session cache and the limits. Most programs never create one. Create one to set limits, or to keep groups of sessions in separate pools, and pass it to Session(engine=...).
| Argument | Meaning |
|---|---|
max_host_connections |
Cap on connections per host for the engine's sessions that use the shared pool or no pool. 0 means no limit. httpperf queues requests above it and reports the wait as queue_time. |
max_total_connections |
Cap on all connections for the same sessions. 0 means no limit. |
max_idle_connections |
How many connections each pool keeps (the shared pool, and each session's own pool). Must be at least 1. |
json_dumps, json_loads |
The JSON functions for the engine's sessions, unless a session sets its own. The defaults use the standard library: compact output, and bodies decoded as UTF-8. See JSON. |
Each asyncio loop has its own default engine, so sessions without an engine work in any thread, and in each asyncio.run(), without setup. A loop's default engine lasts as long as the loop, and is closed once the loop has been closed and no session uses it.
An engine binds to the asyncio loop running when it is first used, and so does a session. An engine serves one loop at a time, and using it from a second live loop raises RuntimeError. Once its loop is closed, as at the end of asyncio.run(), it binds to the next one and keeps its pool. So a session kept between asyncio.run() calls keeps its connections. To run loops in several threads at once with your own engines, give each thread its own Engine.
engine.close() stops the curl thread and closes the shared pool's connections, and later requests raise RuntimeError. Requests still in flight fail with RequestError, and a ResourceWarning says how many there were. with and async with call close() on exit. An engine that is no longer referenced is closed automatically. See docs/connections.md for how these fit together.
Session methods
await session.get(url, **kwargs), and likewisepost,put,patch,delete,headandoptions.await session.request(method, url, **kwargs).session.close(): closes the session's connections once its requests finish. Later requests raiseRuntimeError.withandasync withcall it on exit.session.cookies(): the cookie jar as a dict.session.get_cookie_list(),session.add_cookie_list(cookies),session.erase_all_cookies()andsession.erase_session_cookies(): work withCookieobjects. These are ordinary methods, not coroutines.session.set_response_callback(callback): called with eachResponse, including each hop of a redirect.
Request arguments
| Argument | Meaning |
|---|---|
params |
Query parameters: a dict or list of pairs (lists as values repeat the key), or a ready-made string. Added to any query already in the URL. |
headers |
Dict of headers. |
headers_list |
List of "Name: value" strings, for repeated headers. |
cookies |
Dict of cookies to send with this request (added to the session jar). |
cookie_list |
List of Cookie objects. |
auth |
(username, password) for basic auth. |
data |
Request body: str or bytes as is, with no Content-Type unless you set one, or a dict or list of pairs, form-encoded with Content-Type: application/x-www-form-urlencoded unless you set it. |
json |
Object to send as JSON, encoded with the session's json_dumps. Sets Content-Type: application/json unless you set it. |
files |
Dict (or list of pairs) of files to send as multipart/form-data, with any data dict as extra fields. A value is an open file, or (filename, content) or (filename, content, content_type), where content is bytes, str or a file. Files are read into memory. |
cert |
(certfile, keyfile), overriding the session's certificate. |
verify |
True, False or a CA bundle path, overriding the session's verify. |
timeout, connect_timeout |
Override the session's. timeout=0 removes the session's limit for this request. |
allow_redirects |
Follow redirects (default True; False for head). |
max_redirects |
Default 5. Raises RequestError("Max Redirects") beyond it. |
Failed transfers raise httpperf.RequestError with curl's detailed error message, such as Failed to connect to 127.0.0.1 port 8080 after 0 ms: Couldn't connect to server. Its code is curl's error code. Timeouts raise httpperf.Timeout, a subclass, so they can be counted separately.
Response
| Attribute | Meaning |
|---|---|
status_code |
HTTP status. |
ok |
True if the status is below 400. |
reason |
Reason phrase from the status line, or the standard phrase for HTTP/2 and HTTP/3, which send none. |
raise_for_status() |
Raises httpperf.HTTPError (a RequestError, with the response) for 4xx and 5xx statuses. |
elapsed |
total_time as a timedelta. |
url |
Effective URL. |
redirect_url |
Location of a redirect, or None. |
history |
Earlier responses in a redirect chain. |
http_version |
"HTTP/1.0", "HTTP/1.1", "HTTP/2" or "HTTP/3". |
headers |
Case-insensitive mapping of the response headers. Repeated headers are joined with , , as in requests. headers_tuple keeps repeats and order. Both skip interim responses such as 100 Continue. header is the raw text of every header block, decoded as latin-1. |
body |
Bytes. |
text |
Body decoded with encoding. |
encoding |
From the Content-Type charset, else latin-1 (utf-8 for JSON). Can be set. |
json() |
Body parsed with the session's json_loads, once. By default the standard library, always as UTF-8, as RFC 8259 requires. |
cookies, cookielist |
The cookies this response set, from its Set-Cookie headers, as a dict or as Cookie objects. The session's whole jar is session.cookies(). |
primary_ip |
Address connected to. |
upload_size, download_size |
Bytes, as integers. |
request |
The Request: method, url, headers, cookies, auth, data. |
JSON
By default httpperf uses the standard library's json: compact output for json=, and response bodies decoded as UTF-8 for json(). It needs no extra dependency and has the most scrutinised parser, which matters because load tests often fetch responses from third parties.
If JSON costs too much CPU, pass faster functions as json_dumps and json_loads, on the Engine for all its sessions or on one Session. orjson is a good choice for encoding, and pysimdjson for decoding. Create the parser once, at module scope, since it keeps its buffers between documents:
import httpperf
import orjson
import simdjson
parser = simdjson.Parser()
engine = httpperf.Engine(json_dumps=orjson.dumps, json_loads=parser.parse)
async def journey():
async with httpperf.Session(engine=engine) as session:
r = await session.post("https://example.com/search", json={"q": "httpperf"})
return r.json()["items"][3]["name"]
Things to know:
- orjson is about 8 times faster than
jsonon larger payloads, but turnsNaNintonulland refuses integers over 64 bits. parser.parseis lazy: only the values you touch become Python objects. That was about 8 times faster thanjson.loadsfor reading one field of a 500 KB document. The result is read-only and not a realdictorlist;.as_dict()and.as_list()convert it. Documents stay valid after the parser moves on to the next one.- To get real
dicts andlists from simdjson, usejson_loads=lambda body: parser.parse(body, True). - Request bodies that never change can be encoded once and sent as
data=, withheaders={"Content-Type": "application/json"}.
Timings
All in seconds.
| Attribute | Meaning |
|---|---|
start_time, end_time |
Wall-clock times (time.time()) when the request was made and when Python received the response. |
namelookup_time |
DNS, measured by curl from the start of the transfer. |
connect_time |
TCP connect complete. 0 when the connection was reused. |
appconnect_time |
TLS handshake complete. 0 for plain http and reused connections. |
pretransfer_time |
Ready to send. |
posttransfer_time |
Request fully sent. starttransfer_time − posttransfer_time is the server's time to first byte, without connection setup or upload. None with libcurl older than 8.10. |
starttransfer_time |
First byte received. |
total_time |
Transfer complete. |
queue_time |
Time waiting in httpperf's queue for a connection, under the engine or session limits. 0 if the request did not wait. curl's timings start after it. |
client_lag |
end_time − start_time − total_time − queue_time: time the request spent waiting on Python, before it was sent and after it finished. Measured with the monotonic clock, so clock changes don't affect it. |
curl measures its timings on the curl thread, so a busy Python process does not inflate them. client_lag is how you see that Python is the bottleneck: if it grows, the client cannot keep up, and achieved request rates describe the client rather than the server. Report it alongside response times (p50, p99, max).
queue_time is real waiting that a user would see (a browser's "stalled" time), but it is client-side, so keep it out of server latency.
Known limitations
- curl closes expired idle connections lazily, the next time the pool needs a connection, so the server sees the close late. See docs/connections.md.
- Requests in flight when
Engine.close()is called never complete.
Development
make test
make lint # ruff and clang-format, check only
make lint-fix # apply formatting and fixes
make clean # remove build output, caches and profiler output (keeps .venv)
make distclean # also remove .venv
Each target first creates .venv with uv, if needed, and installs httpperf in editable mode with the dev tools. It reinstalls when setup.py, pyproject.toml or the C sources change, so C edits are rebuilt automatically. make venv does only that step.
make venv PY_VERSION=3.8 VENV=.venv-3.8 builds another venv, and VENV=.venv-3.8 on make test or make lint uses it.
To release, set __version__ in httpperf/version.py (for example 1.0rc1 or 1.0), commit and push to main, then run make release. It tags v<version> and pushes the tag, and the release workflow builds the wheels and publishes them to PyPI.
The tests run local servers: pytest-httpbin, small threaded http.server servers for connection counting and TLS, and hypercorn for HTTP/2 and HTTP/3 (skipped on Python 3.8, where hypercorn's HTTP/3 server hangs on shutdown). Client certificates are generated with openssl. The httpbin server is single-threaded, so keep concurrency in tests low.
Set HTTPPERF_PROFILE=1 when building to instrument the extension. See docs/profiling.md.
Licence
MIT. See LICENSE. NOTICE covers the bundled Redis event library and the libraries included in the binary wheels.
Metadata
Release files for httpperf 1.0rc2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| httpperf-1.0rc2.tar.gz | 65.1 kB | With provenance | Details for httpperf-1.0rc2.tar.gz |
Built distributions (wheels)
Total release size: 127.1 MB
Release files / httpperf-1.0rc2.tar.gz
| Download URL | httpperf-1.0rc2.tar.gz |
|---|---|
| Size | 65.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
29489d83ae323a161ef05599484cf5b552eeac9824276034fa4c73537f9f3786
|
|
BLAKE2b-256 checksum How to use checksums |
6a2e67d1c29fcc2de734adddc0fa5d68874fb50aa0ff7b58b33e5d5205926f7c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp315-cp315-musllinux_1_2_x86_64.whl
| Download URL | httpperf-1.0rc2-cp315-cp315-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.15 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
5b67348b187a0cf218bace8d0b11d5faf362c7e9252df53a12771e663d4554a3
|
|
BLAKE2b-256 checksum How to use checksums |
24ce776ef6ecb79b406415271981c6420e9fea3391d7ab682bd085ae3a111a1c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp315-cp315-musllinux_1_2_aarch64.whl
| Download URL | httpperf-1.0rc2-cp315-cp315-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 4.6 MB |
| Tags | CPython 3.15 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
3877b13c921cbb13999beaa4a73bf2d1100e303511face9d75ac6e3f813385a6
|
|
BLAKE2b-256 checksum How to use checksums |
2561bbe72a4941d2a9bb99371a42814978876f6dec52364ee7f8a50b3af1019d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp315-cp315-manylinux_2_34_x86_64.whl
| Download URL | httpperf-1.0rc2-cp315-cp315-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 4.7 MB |
| Tags | CPython 3.15 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
cc7a2abe1ad07c5522afab79f32edeaa5ea0190dbfadb77a5edb866d7564556d
|
|
BLAKE2b-256 checksum How to use checksums |
3d764d1584c995efe3103cb3d2a2f6dc3320ba1e412b588b4f12114668a14eb6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp315-cp315-manylinux_2_34_aarch64.whl
| Download URL | httpperf-1.0rc2-cp315-cp315-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.15 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
abf4b2bf88808995d97d7101f030f0edd760c0cf140115eb504755663a34d1fd
|
|
BLAKE2b-256 checksum How to use checksums |
9a9b9f605c58120312634aa3361de9016229165c7a2b3893ce65a40f175ea708
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp314-cp314-musllinux_1_2_x86_64.whl
| Download URL | httpperf-1.0rc2-cp314-cp314-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.14 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
aeb27f22073f75dd421158304708c251fdc6ca09c5a8cb0f9f41002e3c6fa056
|
|
BLAKE2b-256 checksum How to use checksums |
bfcd59eb9fa2d4f15615e2784075453c5aad2007a29a2d03eb7748916c222e85
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp314-cp314-musllinux_1_2_aarch64.whl
| Download URL | httpperf-1.0rc2-cp314-cp314-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 4.6 MB |
| Tags | CPython 3.14 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
d1cc414e55856368d7f5b0c9ea9238dbb32d96d0246b9f5d05172418575d1529
|
|
BLAKE2b-256 checksum How to use checksums |
6ab7b83234b272256dff1b1108f233ef6c577799a85c92b03b67a7e2d08eec5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp314-cp314-manylinux_2_34_x86_64.whl
| Download URL | httpperf-1.0rc2-cp314-cp314-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 4.7 MB |
| Tags | CPython 3.14 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
f0acbab54daa6c63a71fd01cba3286bbd43bbd910f9aa6edb52cb48c350c2aed
|
|
BLAKE2b-256 checksum How to use checksums |
f0b8d6d2b9e6b5ae60de8b983cb189c870fd95116e3b6021b5b8a0df663b7d7d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp314-cp314-manylinux_2_34_aarch64.whl
| Download URL | httpperf-1.0rc2-cp314-cp314-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.14 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
a3700dccb86bd54358434629d6f46abe7f812f9c1bd590d0d55dbd90c20228c4
|
|
BLAKE2b-256 checksum How to use checksums |
d162da0b4327412bcd571ecd70ac34ae7abf66cfdd9ed54e4143bbaa595eb692
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp313-cp313-musllinux_1_2_x86_64.whl
| Download URL | httpperf-1.0rc2-cp313-cp313-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.13 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
cb2939f39d2ba8053f03fe504e5e0d8a322c7a60a5117dade96a75adc836fe2a
|
|
BLAKE2b-256 checksum How to use checksums |
547a7f9e7bfe98e23991d45b3c6d8bc6dc281dd58899060046ab32196c570ed1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp313-cp313-musllinux_1_2_aarch64.whl
| Download URL | httpperf-1.0rc2-cp313-cp313-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 4.6 MB |
| Tags | CPython 3.13 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
1ac471903d855f93312f7c0ae6b2343a1e6a75d13c6b9e99fd0f7c62059faf1a
|
|
BLAKE2b-256 checksum How to use checksums |
e8d517e94170e0119cbbb0885e508945c3e996934d86570b43b7172d32c33eb5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp313-cp313-manylinux_2_34_x86_64.whl
| Download URL | httpperf-1.0rc2-cp313-cp313-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 4.7 MB |
| Tags | CPython 3.13 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
383e30bd3bf155bc9f80eeed9cf8734156aa7b6fcd01d24130b34308cf13013b
|
|
BLAKE2b-256 checksum How to use checksums |
507483565c2ac7fa384eb3d47b3dc6ea3443ac4b40193f9a35b516840b742af4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp313-cp313-manylinux_2_34_aarch64.whl
| Download URL | httpperf-1.0rc2-cp313-cp313-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.13 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
c94dce8d6fc1f2d5251d4f7f2e67e863fbb3644f3600b82e52a884130fc50344
|
|
BLAKE2b-256 checksum How to use checksums |
23aa6ca0d76fd0e83f44a68fd80730ccf5956e364ff56c64ae2eb27a68bf4473
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp312-cp312-musllinux_1_2_x86_64.whl
| Download URL | httpperf-1.0rc2-cp312-cp312-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.12 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
faf42b763e0dd92e8b973d218f6fe0a89dc31c4f63de5e5a178cc5af95de5421
|
|
BLAKE2b-256 checksum How to use checksums |
87e2dda1c3ce49c65c31088613644dbdfe5bae72cd6103d211314dbc6d38c4da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp312-cp312-musllinux_1_2_aarch64.whl
| Download URL | httpperf-1.0rc2-cp312-cp312-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 4.6 MB |
| Tags | CPython 3.12 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
15c582d5f81489570b13c8c038d1a55dbb6909116bc28df4fef750fd4bd64d23
|
|
BLAKE2b-256 checksum How to use checksums |
49d12f49a934bd863664ba218f0d7b68dbb96e7a74315cea2350d504dc613b92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp312-cp312-manylinux_2_34_x86_64.whl
| Download URL | httpperf-1.0rc2-cp312-cp312-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 4.7 MB |
| Tags | CPython 3.12 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
1050bce426f801f609293d4061ab9ee74ceb103cd04e4abd19a44485b1cef210
|
|
BLAKE2b-256 checksum How to use checksums |
176040d14b5a376854f376fc5afb2c7e3645e2b0c79e13bb77708eaebbead985
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp312-cp312-manylinux_2_34_aarch64.whl
| Download URL | httpperf-1.0rc2-cp312-cp312-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.12 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
ab81468e8d8150822a1bac3e7ee5424a5f389cd25bffb443058abc5ed1e3b47b
|
|
BLAKE2b-256 checksum How to use checksums |
24ea5601d68c4f7d40ed3925004c2605e542c4656c8b8cbc7b99ba4b65986400
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp311-cp311-musllinux_1_2_x86_64.whl
| Download URL | httpperf-1.0rc2-cp311-cp311-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
44b48b78a51e1e83be2204501d36def76c6121c70e45e1c8a1cf4807ec6e8abb
|
|
BLAKE2b-256 checksum How to use checksums |
8a389ffee1d709874925991e5c06aa4be90fff8d4c690860aaece508e98529bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp311-cp311-musllinux_1_2_aarch64.whl
| Download URL | httpperf-1.0rc2-cp311-cp311-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 4.6 MB |
| Tags | CPython 3.11 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
8048148a69843017164b4bfa7897bf6d855b368137e24fc4fd4ab594b64dc916
|
|
BLAKE2b-256 checksum How to use checksums |
9a800e72eed8d1153b91404b3eb257e93fd14d8f657bafa2c5931bd7c8c3d497
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp311-cp311-manylinux_2_34_x86_64.whl
| Download URL | httpperf-1.0rc2-cp311-cp311-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 4.7 MB |
| Tags | CPython 3.11 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
6f1c20e682c322405a05c394c1f0f7ec5c9ddb3da0601ba8877852f9aaaf649a
|
|
BLAKE2b-256 checksum How to use checksums |
3dc390e40dfd33e83fa3bf43dfc786796d7137d1705c93ecc497c4c00e2adbac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp311-cp311-manylinux_2_34_aarch64.whl
| Download URL | httpperf-1.0rc2-cp311-cp311-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.11 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
8d7df44ec6d97fcb955164ee3d03d06f5c56574d2c4767589cb3b3da1456e5c9
|
|
BLAKE2b-256 checksum How to use checksums |
736947b3f9354d82acd9c6a44d9459f0fbd16856b92cd2302287edef8782f8c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp310-cp310-musllinux_1_2_x86_64.whl
| Download URL | httpperf-1.0rc2-cp310-cp310-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.10 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
1dfb19acb95d01be646abe1b606fef9ba758bcaf9a050748c01b40b2fb59492a
|
|
BLAKE2b-256 checksum How to use checksums |
53c934db65c724cad6327b72e04c92c5d1ec263984749c07d5036e94490b300f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp310-cp310-musllinux_1_2_aarch64.whl
| Download URL | httpperf-1.0rc2-cp310-cp310-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 4.6 MB |
| Tags | CPython 3.10 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
9c29e2cf7c1c93b26b353c0003f930416fe67af3c1f772b8828cd9ae827637ab
|
|
BLAKE2b-256 checksum How to use checksums |
a51484c8c909cfa3e45b251e547d24979f0c176328338817d002515912833a70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp310-cp310-manylinux_2_34_x86_64.whl
| Download URL | httpperf-1.0rc2-cp310-cp310-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 4.7 MB |
| Tags | CPython 3.10 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
f175f39d6275b98665649a773590273966a7586cbb64a98956e3b708e0881bec
|
|
BLAKE2b-256 checksum How to use checksums |
0ffbafb773c30c66aded01fcc391dc16064628f4ce6bb7b7bcd4aa8d851ce571
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp310-cp310-manylinux_2_34_aarch64.whl
| Download URL | httpperf-1.0rc2-cp310-cp310-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.10 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
7575230a2c3632ced2825baa0362f22c2d9f84bb9d5d5d480bbe471d4990ad91
|
|
BLAKE2b-256 checksum How to use checksums |
41efd8ec25f014f91b3b1b55d0f37ea4fbb904f7bef8ba211d0c8ac52465b994
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp39-cp39-musllinux_1_2_x86_64.whl
| Download URL | httpperf-1.0rc2-cp39-cp39-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.9 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
5a5b79707044f1d6edd4bb1fa6bea72eb192ecefaacf3eac3707c21aaca921c2
|
|
BLAKE2b-256 checksum How to use checksums |
7b9cad0432bf0972ad93b14c2d013d1b8e374d4e0d443865471c454e89ca485a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp39-cp39-musllinux_1_2_aarch64.whl
| Download URL | httpperf-1.0rc2-cp39-cp39-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 4.6 MB |
| Tags | CPython 3.9 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
6718d4104a68af463388973b93a45e72f900e4fcfc8181d0d5167ee809e64a75
|
|
BLAKE2b-256 checksum How to use checksums |
56cd46b72c62a2316dd1f8b46c07eaee4125a7945802f395315f00bd68dcc7fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp39-cp39-manylinux_2_34_x86_64.whl
| Download URL | httpperf-1.0rc2-cp39-cp39-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 4.7 MB |
| Tags | CPython 3.9 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
a8127e6fa61a98b32961537288f44216b7533ae507dec4c09744e74ca3f97629
|
|
BLAKE2b-256 checksum How to use checksums |
99e1a071456628167e87ba45b931296b8c63c81ef5ec7d6981a90634215d4480
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / httpperf-1.0rc2-cp39-cp39-manylinux_2_34_aarch64.whl
| Download URL | httpperf-1.0rc2-cp39-cp39-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.9 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
15de2c45d390f8fa8485e831b8c8af1fd50f0357d9d0ff652a2e1b9290c37181
|
|
BLAKE2b-256 checksum How to use checksums |
df146432dec6d6e07b69537b97ae0546ea30d446da0f02174540095270e378ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logSecurity for httpperf 1.0rc2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 29 files in this release have been uploaded with provenance metadata.
Attestation for httpperf-1.0rc2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.