Skip to main content

ssrJSON-benchmark

PyPI - Version PyPI - Wheel

The ssrJSON benchmark repository.

Benchmark Results

The benchmark results can be found in website results or GitHub results. Contributing your benchmark result is welcomed.

Quick jump for

Usage

pip install ssrjson-benchmark[all]  # Install all dependencies for benchmarking and printing PDF / Markdown
# pip install ssrjson-benchmark[benchmark]  # Only install third-party JSON libraries for benchmarking
# pip install ssrjson-benchmark[visual]  # Only install dependencies for generating PDF / Markdown report
# pip install ssrjson-benchmark  # Clean install without any dependency
python -m ssrjson_benchmark full -h # Run benchmark + generate PDF report in one command
# python -m ssrjson_benchmark benchmark -h  # Run benchmark and generate JSON benchmark result
# python -m ssrjson_benchmark print -h # Generate report from previously saved JSON benchmark result

To contribute a result, run the defaults in five fresh processes (about 20 minutes on a Ryzen 9 9900X):

python -m ssrjson_benchmark full --runs 5

For a quick local check, python -m ssrjson_benchmark full --locality hot takes about two minutes.

Notes

  • Libraries benchmarked are json, ujson, pydantic, msgspec, orjson and ssrJSON; where a library only produces the other output type, a single decode("utf-8") / encode("utf-8") is appended rather than dropping it from the comparison.
  • The UTF-8 cache is a dumps_to_bytes concern only, since dumps_to_str and loads never encode a str to UTF-8.
  • The cache is primed with orjson.dumps, and cache-related groups are skipped for all-ASCII inputs because ASCII PyUnicode carries no separate UTF-8 buffer to invalidate.
  • A fresh input object is built per measured call only when the relevant data is non-ASCII, and "relevant" differs per test: loads str depends on the source document, dumps on the parsed object (github.json is ASCII text whose \uXXXX escapes decode to non-ASCII strings).
  • msgspec is absent from the indented groups because it has no indent option, and msgspec.json.format re-parses finished output, which is a different operation.
  • hot keeps one live copy so the object is in cache when the call starts, while cold rotates a ring sized at a multiple of the last level cache (--cold-working-set-multiple) so every measured object has been evicted by the same number of intervening copies.
  • Fresh objects in a cold ring are used once each, and the whole ring is freed and rebuilt when it runs out instead of refilling a slot after every call, because a copy built while its neighbours are alive reuses pymalloc's free lists in reverse order: a cold github.json dump took about 13µs on a copy from a whole-ring build and 30-40µs on a refilled one, so call order alone made one library look twice as fast as another.
  • The first few calls after a rebuild run up to 1.6x slow (ctm.json: orjson's first four, ssrJSON's first two), so every rebuild is followed by 8 unmeasured calls, without which ctm.json measured 44% slow on a 2x ring that had to be rebuilt mid-chunk.
  • Hot frees its copy before building the next one, for the same reason: building while the old copy was alive made hot ctm.json dumps drift from 300µs to 900µs over a run, penalising whichever library ran later, while freeing first holds them at 230-270µs.
  • The cold ring defaults to 8x the LLC because there every bundled file's cold dumps were within 2.5% of a 16x ring, while smaller rings were off by up to 40% (instruments.json at 1x, twitter.json by 14-16% at 1x and 2x), whereas loads read their input sequentially and the prefetcher keeps them within a few percent of hot at any size.
  • ssrJSON build in the header records whether the extension is PGO-optimized (as reported by ssrJSON 0.0.20 and later), how it was installed (package index, nix, a local source tree, or a git commit), the compiler named in the binary, and assertions on for a build without NDEBUG, because a pip install from source reports the same version as the release wheel yet is built without PGO unless SSRJSON_ENABLE_PGO=1 is set, and a Debug build is -O0.
  • An LLC source of fallback in the header means detection failed and cold results are not comparable across machines, so set --llc-bytes explicitly.
  • --bin-process-megabytes is deprecated and ignored, because it used to control how cold the measured object was through what looked like a memory-only knob.
  • --min-iterations exists because an equal-bytes budget alone leaves the largest inputs with only a few dozen samples.
  • The defaults are 100 iterations and 0.05 GiB per test case because beyond ~60 samples the median's interval is a fraction of a percent hot (about a percent cold), far below the run-to-run spread that --runs exposes, so --min-iterations 200 --process-gigabytes 0.1 restores the previous, ~3x slower budget.
  • Contributed results use --runs 5 rather than a larger --process-gigabytes, because run-to-run spread (median 1.7%, p90 3.3% across three processes) is about eight times the within-process interval, and only more processes reduce it.
  • Pinning is on by default because an unpinned process on a hybrid CPU can land on an efficiency core and invert which library wins, not merely add noise.
  • min, median, mean and p95 are all recorded in the JSON, since mean and min genuinely disagree about the winner when two libraries have different noise profiles.
  • Error bars are the distribution-free confidence interval of the charted statistic, or the run-to-run range under --runs > 1, not the standard deviation of a single iteration, and the Runs line of the header says which.
  • Under --runs > 1 each process contributes one ratio per library, its json time over that library's time measured alongside it, and the bar is the median of those with their range, because pairing json's fastest process with another library's slowest counts a whole-process slowdown twice and puts a bar on json's own 1x.
  • Libraries are interleaved across --rounds chunks in rotating order, so slow drift such as thermal throttling hits every library equally instead of penalising whichever runs last.
  • --runs N repeats the whole benchmark in N fresh processes, which is the only way to see binary and heap layout effects, and those are the size of the gap between the closest libraries.
  • Every library's output is verified to round-trip before it is timed, so a mismatch aborts unless --allow-output-mismatch is passed, which hatches and marks the offending bars instead.
  • The stdlib json baseline uses separators=(",", ":"), because its default separators emit ~7% more bytes and inflated every ratio measured against it.
  • Only the call itself is timed: building the input and freeing the result both sit outside the measured window.
  • The C timing loop makes each library's call itself, with that library's own arguments, because wrapping only the libraries that need an argument or a conversion in a Python lambda charged them ~10ns that the others skipped, a sizeable share of a small call.
  • The clock is CLOCK_MONOTONIC on Linux, CLOCK_UPTIME_RAW on macOS, whose CLOCK_MONOTONIC only has microsecond resolution, and QueryPerformanceCounter on Windows.
  • A call shorter than 100 clock steps (the resolution in the header) is timed in batches per sample, one batch size for every library in a group, because the median of samples rounded to a coarse clock snaps to a whole step: on a 1µs clock a 750ns and a 960ns call come out tied.
  • A fresh process keeps its core busy for half a second before measuring, because an idle core can take tens of milliseconds to reach full clock (24% slow for the first 75ms on a Ryzen 9 9900X under amd-pstate-epp).
  • The garbage collector is off while measuring, which slightly understates the fast libraries: with it on, json loads of twitter.json took 4.7% longer while orjson and ssrJSON were unaffected.
  • The summary has one panel per operation, since ratios to json for loads and dumps sit on very different scales and a pooled average mostly reflects how many points each operation contributes.
  • Each document is one value in a summary box, the geometric mean over that operation's groups, so a non-ASCII file does not outweigh an ASCII one by having the extra cached-dumps group, and the whiskers reach the slowest and fastest document rather than hiding any as outliers.
  • In the loads panel a pretty-printed document counts through its .min.json twin, because compact JSON is what loads meets in practice, and both remain charted.
  • Every library in the summary runs in the configuration its wheel ships with, including ssrJSON's UTF-8 cache writing, so dumps to bytes (no cache write) is charted per file but left out of the summary: it forces ssrJSON out of its default to isolate the cache-write cost.
  • In the hot dumps-to-bytes section, a non-ASCII file's chart shows the UTF-8 cache break-even, how many dumps of one object it takes before writing the cache pays for itself (ssrjson.write_utf8_cache(False) is faster below it), and files whose cache-write cost is below the measurement's resolution get no break-even, which under --runs > 1 means the cost has to show in every process, with the break-even the median of each process's own, since a process that is slow overall moves all three groups together.
  • Using your own dataset needs no code changes, just point -d at a directory of *.json files and everything per-file is derived from the data.
  • Each input that is at least 1% insignificant whitespace is also measured as a <name>.min.json twin in the same run, loads only, because the bundled files are pretty-printed while most JSON on the wire is compact (ctm.json is 70% whitespace, twitter.json 38%).
  • The twin is made by deleting whitespace outside string literals rather than by re-serializing, which would also rewrite number spellings and \uXXXX escapes, and --no-compact turns it off.
  • Data the libraries disagree about aborts the run, which in practice means integers wider than 64 bits (rejected by orjson and ssrJSON) and NaN/Infinity (rejected by orjson and msgspec).
  • Peak memory is a single cold ring, --cold-working-set-multiple times the LLC, because every library walks the same ring with one running call count.
  • ssrJSON, msgspec, orjson and pydantic_core keep short strings cached across calls, so parsing one document over and over is their best case: when every call brought dict keys never seen before, loads of a 100KB slice of twitter.json slowed by 22% (ssrJSON), 18% (msgspec), 10-14% (orjson, pydantic_core), 7% (ujson) and 2% (json), so the results fit a service that parses one schema repeatedly and flatter one whose keys keep changing.
  • songci.json is the real-world CJK document, kept as one all-UCS2 case because none of its strings has a character outside the BMP: 1,000 Song ci poems, unmodified 宋词/ci.song.0.json from chinese-poetry (MIT License, Copyright (c) 2016 JackeyGao).

Metadata

Release files for ssrjson-benchmark 0.0.12

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ssrjson-benchmark 0.0.12
File Size Uploaded Provenance Actions
ssrjson_benchmark-0.0.12.tar.gz 1.1 MB With provenance Details for ssrjson_benchmark-0.0.12.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for ssrjson-benchmark 0.0.12
File Actions
ssrjson_benchmark-0.0.12-cp314-cp314t-win_amd64.whl CPython 3.14 CPython 3.14 free-threading Windows x86-64 Details for ssrjson_benchmark-0.0.12-cp314-cp314t-win_amd64.whl
ssrjson_benchmark-0.0.12-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 Details for ssrjson_benchmark-0.0.12-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
ssrjson_benchmark-0.0.12-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for ssrjson_benchmark-0.0.12-cp314-cp314-win_amd64.whl
ssrjson_benchmark-0.0.12-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ x86-64 Details for ssrjson_benchmark-0.0.12-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
ssrjson_benchmark-0.0.12-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for ssrjson_benchmark-0.0.12-cp313-cp313-win_amd64.whl
ssrjson_benchmark-0.0.12-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64 Details for ssrjson_benchmark-0.0.12-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
ssrjson_benchmark-0.0.12-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for ssrjson_benchmark-0.0.12-cp312-cp312-win_amd64.whl
ssrjson_benchmark-0.0.12-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64 Details for ssrjson_benchmark-0.0.12-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
ssrjson_benchmark-0.0.12-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for ssrjson_benchmark-0.0.12-cp311-cp311-win_amd64.whl
ssrjson_benchmark-0.0.12-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64 Details for ssrjson_benchmark-0.0.12-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
ssrjson_benchmark-0.0.12-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for ssrjson_benchmark-0.0.12-cp310-cp310-win_amd64.whl
ssrjson_benchmark-0.0.12-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.17+ x86-64 Details for ssrjson_benchmark-0.0.12-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Total release size: 15.2 MB

Release files / ssrjson_benchmark-0.0.12.tar.gz

Download URL ssrjson_benchmark-0.0.12.tar.gz
Size 1.1 MB
Tags Source
SHA-256 checksum
How to use checksums
cf357d53bc93acfb583966002e97ba061069faefd00a7dd4ab597bf7b6cf4aba
BLAKE2b-256 checksum
How to use checksums
58a0ea486d27b36dc1775aafe1db09060346615ef7f3ef819e7b61e734d87178
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 18, 2026.

Transparency log

Release files / ssrjson_benchmark-0.0.12-cp314-cp314t-win_amd64.whl

Download URL ssrjson_benchmark-0.0.12-cp314-cp314t-win_amd64.whl
Size 1.2 MB
Tags CPython 3.14 CPython 3.14 free-threading Windows x86-64
SHA-256 checksum
How to use checksums
25ccdc207e1217efebfa4505290dd8f25c6afc6772e3a5c7cceb0c84cdc41643
BLAKE2b-256 checksum
How to use checksums
aa29e05c4118773eed9a948da513ae9c22220ce31894abdf65efd0d6c05f6e3c
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 18, 2026.

Transparency log

Release files / ssrjson_benchmark-0.0.12-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL ssrjson_benchmark-0.0.12-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 1.2 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
6cdf62a42e803d3b72725c7d6c398773e94f5342cd2f8492261826449e5441db
BLAKE2b-256 checksum
How to use checksums
1a90c5ac96717bc14f940df65ec820fa798a4efd2428cb347b890962af791efc
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 18, 2026.

Transparency log

Release files / ssrjson_benchmark-0.0.12-cp314-cp314-win_amd64.whl

Download URL ssrjson_benchmark-0.0.12-cp314-cp314-win_amd64.whl
Size 1.2 MB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
e28d6df37d80c503f0dfe6b7913904c76b911b3567da33bc0961352b63036cf8
BLAKE2b-256 checksum
How to use checksums
c9cae1ed04016e2e6c37055f0741233bc2fe688c66136f076c49c92939baba7c
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 18, 2026.

Transparency log

Release files / ssrjson_benchmark-0.0.12-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL ssrjson_benchmark-0.0.12-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 1.2 MB
Tags CPython 3.14 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
3dd9fce4d63e0b05cdb34d47b4664f3aa160087b9b3521ccae2c967653603c55
BLAKE2b-256 checksum
How to use checksums
3614054ffd9b7a00a0295c10e510b981cce46e2e730b572300b527219b69e4c0
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 18, 2026.

Transparency log

Release files / ssrjson_benchmark-0.0.12-cp313-cp313-win_amd64.whl

Download URL ssrjson_benchmark-0.0.12-cp313-cp313-win_amd64.whl
Size 1.2 MB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
d350a6f717e4a59b516ae7b86bb86b495ae734d94637c9e7197a92ce7f392fac
BLAKE2b-256 checksum
How to use checksums
7fe67f219475fadb7591aa01f375424aab6f45cbd90219499ff62cd5d6b3ff6c
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 18, 2026.

Transparency log

Release files / ssrjson_benchmark-0.0.12-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL ssrjson_benchmark-0.0.12-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 1.2 MB
Tags CPython 3.13 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
c41236fc60e54a05cba8e7d0da73ee26c54b1e5de14aea4e1b0248a2651f3fdd
BLAKE2b-256 checksum
How to use checksums
6e87afbb19e17247d5040b6bdc275209f1ad9f319391b6fa4e1a9f5a599b31d2
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 18, 2026.

Transparency log

Release files / ssrjson_benchmark-0.0.12-cp312-cp312-win_amd64.whl

Download URL ssrjson_benchmark-0.0.12-cp312-cp312-win_amd64.whl
Size 1.2 MB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
acf421930caa9eead65503b931b53cfbdb48fcb58350aabe60621b1abead6e70
BLAKE2b-256 checksum
How to use checksums
4294d9514ecb48293d4b38f95c171505ad8d60facb9149ca1841e92cff38e392
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 18, 2026.

Transparency log

Release files / ssrjson_benchmark-0.0.12-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL ssrjson_benchmark-0.0.12-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 1.2 MB
Tags CPython 3.12 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
4a64632a301133397fa151f64f4c40f6b3778880ddd8ecbaf995d9c4a3b7c24d
BLAKE2b-256 checksum
How to use checksums
cf2dfb37fa3250aa8a89896d2a157c90131fb131250b30821bc050b0d6ccbf57
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 18, 2026.

Transparency log

Release files / ssrjson_benchmark-0.0.12-cp311-cp311-win_amd64.whl

Download URL ssrjson_benchmark-0.0.12-cp311-cp311-win_amd64.whl
Size 1.2 MB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
de6f49c7e22b8aadb5e2cc550cbbaa481aa85136ec5f5364fd3079bc473df601
BLAKE2b-256 checksum
How to use checksums
5d5933d4ca7b808afa463ca66ca730e3ebe44bb4ba0c6f92a1edc92dea54b236
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 18, 2026.

Transparency log

Release files / ssrjson_benchmark-0.0.12-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL ssrjson_benchmark-0.0.12-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 1.2 MB
Tags CPython 3.11 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
9ebfdfdb180c7e2c4d0765b3189e68009b0883329747116cb8bdf49b3bb68c54
BLAKE2b-256 checksum
How to use checksums
2102ffd559674a4c7dc702de3bbcfb851f5145d6386fbb8ab511a5c687324854
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 18, 2026.

Transparency log

Release files / ssrjson_benchmark-0.0.12-cp310-cp310-win_amd64.whl

Download URL ssrjson_benchmark-0.0.12-cp310-cp310-win_amd64.whl
Size 1.2 MB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
6f319828f56de37f073e18a2ebf272bf32e9571d3a1c8e5bcd758c5a9ac93c29
BLAKE2b-256 checksum
How to use checksums
00ce21f776a2488f71add56d5bf453c9ae65a3cb5b868adccd09129a782f7297
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 18, 2026.

Transparency log

Release files / ssrjson_benchmark-0.0.12-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL ssrjson_benchmark-0.0.12-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 1.2 MB
Tags CPython 3.10 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
ceb101d96061dc9a00b746a58186dcdac0099e2f24e4b19f4b83a8229fdea7ff
BLAKE2b-256 checksum
How to use checksums
889db65d8b902ce8e4a05dfabdae729a936e5a93dcbf7dbc16f3e1bb9b492dc9
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 18, 2026.

Transparency log

Security for ssrjson-benchmark 0.0.12

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 13 files in this release have been uploaded with provenance metadata.

Select from 13 files

Attestation for ssrjson_benchmark-0.0.12.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 18, 2026.

Transparency log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page