ssrjson-benchmark 0.0.1a0__tar.gz → 0.0.1rc1__tar.gz

{ssrjson_benchmark-0.0.1a0/src/ssrjson_benchmark.egg-info → ssrjson_benchmark-0.0.1rc1}/PKG-INFO

@@ -1,50 +1,48 @@
 Metadata-Version: 2.4
-Name: ssrjson_benchmark
-Version: 0.0.1a0
-Summary: Benchmark for ssrJSON
+Name: ssrjson-benchmark
+Version: 0.0.1rc1
+Summary: benchmark of ssrJSON
+Author-email: Eritque Arcus <eritque-arcus@ikuyo.dev>, Antares <antares0982@gmail.com>
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/Nambers/ssrJSON-benchmark
+Project-URL: Issues, https://github.com/Nambers/ssrJSON-benchmark/issues
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Topic :: System :: Benchmark
+Classifier: Programming Language :: Python :: 3
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.9
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: ssrjson
-Requires-Dist: orjson
-Requires-Dist: matplotlib
-Provides-Extra: all
-Requires-Dist: svglib; extra == "all"
-Requires-Dist: reportlab; extra == "all"
-Requires-Dist: py-cpuinfo; extra == "all"
-Dynamic: description
-Dynamic: description-content-type
 Dynamic: license-file
-Dynamic: provides-extra
-Dynamic: requires-dist
-Dynamic: summary
 
 # ssrJSON-benchmark
 
+<div align="center">
+
+[![PyPI - Version](https://img.shields.io/pypi/v/ssrjson-benchmark)](https://pypi.org/project/ssrjson-benchmark/) [![PyPI - Wheel](https://img.shields.io/pypi/wheel/ssrjson-benchmark)](https://pypi.org/project/ssrjson-benchmark/)
+
 The [ssrJSON](https://github.com/Antares0982/ssrjson) benchmark repository.
 
+</div>
+
 ## Benchmark Results
 
-The benchmark results can be found in [results](results). Contributing your benchmark result is welcomed.
+The benchmark results can be found in [website results](https://ikuyo.dev/ssrJSON-benchmark/) or [GitHub results](https://github.com/Nambers/ssrJSON-benchmark/tree/main/results). Contributing your benchmark result is welcomed.
 
 Quick jump for
 
-* [x86-64-v2, SSE4.2](results/SSE4.2)
-* [x86-64-v3, AVX2](results/AVX2)
-* [x86-64-v4, AVX512](results/AVX512)
+* [x86-64-v2, SSE4.2](https://github.com/Nambers/ssrJSON-benchmark/tree/main/results/SSE4.2)
+* [x86-64-v3, AVX2](https://github.com/Nambers/ssrJSON-benchmark/tree/main/results/AVX2)
+* [x86-64-v4, AVX512](https://github.com/Nambers/ssrJSON-benchmark/tree/main/results/AVX512)
 
 ## Usage
 
-To generate a benchmark report, you need to install `ssrJSON` either by fetched [PyPi](https://pypi.org/project/ssrjson/) or built from [source](https://github.com/Antares0982/ssrjson), and toolkit(`ssrjson_benchmark`) from this repo by:
-
-```bash
-python -m build
-pip install dist/*.whl
-```
-
-Then run the benchmark script:
-
 ```bash
-python benchmark.py
+# you may need to install `svglib`, `reportlab` and `py-cpuinfo` as well
+pip install ssrjson-benchmark
+python -m ssrjson_benchmark
 ```
 
 ## Benchmark options
@@ -56,9 +54,6 @@ python benchmark.py
 ## Notes
 
 * This repository conducts benchmarking using json, orjson, and ssrJSON. The `dumps` benchmark produces str objects, comparing three operations: `json.dumps`, `orjson.dumps` followed by decode, and `ssrjson.dumps`. The `dumps_to_bytes` benchmark produces bytes objects, comparing three functions: `json.dumps` followed by encode, `orjson.dumps`, and `ssrjson.dumps_to_bytes`.
-* The ssrJSON built with the `BUILD_BENCHMARK` option includes several additional C functions specifically designed for executing benchmarks. These functions utilize high-precision timing APIs, and within the loop, only the time spent on the actual `PyObject_Call` invocations is measured.
-* When orjson handles non-ASCII strings, if the cache of the `PyUnicodeObject`’s UTF-8 representation does not exist, it invokes the `PyUnicode_AsUTF8AndSize` function to obtain the UTF-8 encoding. This function then caches the UTF-8 representation within the `PyUnicodeObject`. If the same `PyUnicodeObject` undergoes repeated encode-decode operations, subsequent calls after the initial one will execute more quickly due to this caching. However, in real-world production scenarios, it is uncommon to perform JSON encode-decode repeatedly on the exact same string object; even identical strings are unlikely to be the same object instance. To achieve benchmark results that better reflect practical use cases, we employ `ssrjson.run_unicode_accumulate_benchmark` and `benchmark_invalidate_dump_cache` functions, which ensure that new `PyUnicodeObject`s are different for each input every time.
-
+* When orjson handles non-ASCII strings, if the cache of the `PyUnicodeObject`’s UTF-8 representation does not exist, it invokes the `PyUnicode_AsUTF8AndSize` function to obtain the UTF-8 encoding. This function then caches the UTF-8 representation within the `PyUnicodeObject`. If the same `PyUnicodeObject` undergoes repeated encode-decode operations, subsequent calls after the initial one will execute more quickly due to this caching. However, in real-world production scenarios, it is uncommon to perform JSON encode-decode repeatedly on the exact same string object; even identical strings are unlikely to be the same object instance. To achieve benchmark results that better reflect practical use cases, we employ `ssrjson.run_unicode_accumulate_benchmark` and `benchmark_invalidate_dump_cache` functions, which ensure that new `PyUnicodeObject`s are different for each input every time. (ref: [orjson#586](https://github.com/ijl/orjson/issues/586))
 * The performance of JSON encoding is primarily constrained by the speed of writing to the buffer, whereas decoding performance is mainly limited by the frequent invocation of CPython interfaces for object creation. During decoding, both ssrJSON and orjson employ short key caching to reduce the number of object creations, and this caching mechanism is global in both cases. As a result, decoding benchmark tests may not accurately reflect the conditions encountered in real-world production environments.
-
 * The files simple_object.json and simple_object_zh.json do not represent real-world data; they are solely used to compare the performance of the fast path. Therefore, the benchmark results should not be interpreted as indicative of actual performance.

{ssrjson_benchmark-0.0.1a0 → ssrjson_benchmark-0.0.1rc1}/README.md

@@ -1,30 +1,29 @@
 # ssrJSON-benchmark
 
+<div align="center">
+
+[![PyPI - Version](https://img.shields.io/pypi/v/ssrjson-benchmark)](https://pypi.org/project/ssrjson-benchmark/) [![PyPI - Wheel](https://img.shields.io/pypi/wheel/ssrjson-benchmark)](https://pypi.org/project/ssrjson-benchmark/)
+
 The [ssrJSON](https://github.com/Antares0982/ssrjson) benchmark repository.
 
+</div>
+
 ## Benchmark Results
 
-The benchmark results can be found in [results](results). Contributing your benchmark result is welcomed.
+The benchmark results can be found in [website results](https://ikuyo.dev/ssrJSON-benchmark/) or [GitHub results](https://github.com/Nambers/ssrJSON-benchmark/tree/main/results). Contributing your benchmark result is welcomed.
 
 Quick jump for
 
-* [x86-64-v2, SSE4.2](results/SSE4.2)
-* [x86-64-v3, AVX2](results/AVX2)
-* [x86-64-v4, AVX512](results/AVX512)
+* [x86-64-v2, SSE4.2](https://github.com/Nambers/ssrJSON-benchmark/tree/main/results/SSE4.2)
+* [x86-64-v3, AVX2](https://github.com/Nambers/ssrJSON-benchmark/tree/main/results/AVX2)
+* [x86-64-v4, AVX512](https://github.com/Nambers/ssrJSON-benchmark/tree/main/results/AVX512)
 
 ## Usage
 
-To generate a benchmark report, you need to install `ssrJSON` either by fetched [PyPi](https://pypi.org/project/ssrjson/) or built from [source](https://github.com/Antares0982/ssrjson), and toolkit(`ssrjson_benchmark`) from this repo by:
-
-```bash
-python -m build
-pip install dist/*.whl
-```
-
-Then run the benchmark script:
-
 ```bash
-python benchmark.py
+# you may need to install `svglib`, `reportlab` and `py-cpuinfo` as well
+pip install ssrjson-benchmark
+python -m ssrjson_benchmark
 ```
 
 ## Benchmark options
@@ -36,9 +35,6 @@ python benchmark.py
 ## Notes
 
 * This repository conducts benchmarking using json, orjson, and ssrJSON. The `dumps` benchmark produces str objects, comparing three operations: `json.dumps`, `orjson.dumps` followed by decode, and `ssrjson.dumps`. The `dumps_to_bytes` benchmark produces bytes objects, comparing three functions: `json.dumps` followed by encode, `orjson.dumps`, and `ssrjson.dumps_to_bytes`.
-* The ssrJSON built with the `BUILD_BENCHMARK` option includes several additional C functions specifically designed for executing benchmarks. These functions utilize high-precision timing APIs, and within the loop, only the time spent on the actual `PyObject_Call` invocations is measured.
-* When orjson handles non-ASCII strings, if the cache of the `PyUnicodeObject`’s UTF-8 representation does not exist, it invokes the `PyUnicode_AsUTF8AndSize` function to obtain the UTF-8 encoding. This function then caches the UTF-8 representation within the `PyUnicodeObject`. If the same `PyUnicodeObject` undergoes repeated encode-decode operations, subsequent calls after the initial one will execute more quickly due to this caching. However, in real-world production scenarios, it is uncommon to perform JSON encode-decode repeatedly on the exact same string object; even identical strings are unlikely to be the same object instance. To achieve benchmark results that better reflect practical use cases, we employ `ssrjson.run_unicode_accumulate_benchmark` and `benchmark_invalidate_dump_cache` functions, which ensure that new `PyUnicodeObject`s are different for each input every time.
-
+* When orjson handles non-ASCII strings, if the cache of the `PyUnicodeObject`’s UTF-8 representation does not exist, it invokes the `PyUnicode_AsUTF8AndSize` function to obtain the UTF-8 encoding. This function then caches the UTF-8 representation within the `PyUnicodeObject`. If the same `PyUnicodeObject` undergoes repeated encode-decode operations, subsequent calls after the initial one will execute more quickly due to this caching. However, in real-world production scenarios, it is uncommon to perform JSON encode-decode repeatedly on the exact same string object; even identical strings are unlikely to be the same object instance. To achieve benchmark results that better reflect practical use cases, we employ `ssrjson.run_unicode_accumulate_benchmark` and `benchmark_invalidate_dump_cache` functions, which ensure that new `PyUnicodeObject`s are different for each input every time. (ref: [orjson#586](https://github.com/ijl/orjson/issues/586))
 * The performance of JSON encoding is primarily constrained by the speed of writing to the buffer, whereas decoding performance is mainly limited by the frequent invocation of CPython interfaces for object creation. During decoding, both ssrJSON and orjson employ short key caching to reduce the number of object creations, and this caching mechanism is global in both cases. As a result, decoding benchmark tests may not accurately reflect the conditions encountered in real-world production environments.
-
 * The files simple_object.json and simple_object_zh.json do not represent real-world data; they are solely used to compare the performance of the fast path. Therefore, the benchmark results should not be interpreted as indicative of actual performance.

ssrjson_benchmark-0.0.1rc1/pyproject.toml

@@ -0,0 +1,28 @@
+[build-system]
+requires = ["setuptools >= 77.0.3"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "ssrjson-benchmark"
+version = "0.0.1rc1"
+authors = [
+  { name="Eritque Arcus", email="eritque-arcus@ikuyo.dev" },
+  { name = "Antares", email = "antares0982@gmail.com" }
+]
+description = "benchmark of ssrJSON"
+readme = "README.md"
+requires-python = ">=3.9"
+classifiers = [
+    "Development Status :: 5 - Production/Stable",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "Topic :: System :: Benchmark",
+    "Programming Language :: Python :: 3",
+    "Operating System :: OS Independent",
+]
+license = "MIT"
+license-files = ["LICENSE"]
+
+[project.urls]
+Homepage = "https://github.com/Nambers/ssrJSON-benchmark"
+Issues = "https://github.com/Nambers/ssrJSON-benchmark/issues"

{ssrjson_benchmark-0.0.1a0 → ssrjson_benchmark-0.0.1rc1}/src/benchmark.c

@@ -23,7 +23,7 @@
 #include <Python.h>
 #include <stdbool.h>
 
-#define SSRJSON_BENCHMARK_VERSION "0.0.1a0"
+#define SSRJSON_BENCHMARK_VERSION "0.0.1rc1"
 
 /** compiler builtin check (since gcc 10.0, clang 2.6, icc 2021) */
 #ifndef has_builtin

{ssrjson_benchmark-0.0.1a0 → ssrjson_benchmark-0.0.1rc1}/src/ssrjson_benchmark/__init__.py

@@ -4,10 +4,12 @@ from .benchmark_main import (
     generate_report,
     run_benchmark_default,
 )
+from ._ssrjson_benchmark import __version__
 
 __all__ = [
     "run_benchmark",
     "generate_report_markdown",
     "generate_report",
     "run_benchmark_default",
+    "__version__",
 ]

{ssrjson_benchmark-0.0.1a0 → ssrjson_benchmark-0.0.1rc1}/src/ssrjson_benchmark/benchmark_main.py

@@ -263,7 +263,7 @@ def run_file_benchmark(
 
 
 def get_head_rev_name():
-    return ssrjson.__version__
+    return getattr(ssrjson, "__version__", None) or getattr(ssrjson, "ssrjson").__version__
 
 
 def get_real_output_file_name():

{ssrjson_benchmark-0.0.1a0 → ssrjson_benchmark-0.0.1rc1/src/ssrjson_benchmark.egg-info}/PKG-INFO

@@ -1,50 +1,48 @@
 Metadata-Version: 2.4
-Name: ssrjson_benchmark
-Version: 0.0.1a0
-Summary: Benchmark for ssrJSON
+Name: ssrjson-benchmark
+Version: 0.0.1rc1
+Summary: benchmark of ssrJSON
+Author-email: Eritque Arcus <eritque-arcus@ikuyo.dev>, Antares <antares0982@gmail.com>
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/Nambers/ssrJSON-benchmark
+Project-URL: Issues, https://github.com/Nambers/ssrJSON-benchmark/issues
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Topic :: System :: Benchmark
+Classifier: Programming Language :: Python :: 3
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.9
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: ssrjson
-Requires-Dist: orjson
-Requires-Dist: matplotlib
-Provides-Extra: all
-Requires-Dist: svglib; extra == "all"
-Requires-Dist: reportlab; extra == "all"
-Requires-Dist: py-cpuinfo; extra == "all"
-Dynamic: description
-Dynamic: description-content-type
 Dynamic: license-file
-Dynamic: provides-extra
-Dynamic: requires-dist
-Dynamic: summary
 
 # ssrJSON-benchmark
 
+<div align="center">
+
+[![PyPI - Version](https://img.shields.io/pypi/v/ssrjson-benchmark)](https://pypi.org/project/ssrjson-benchmark/) [![PyPI - Wheel](https://img.shields.io/pypi/wheel/ssrjson-benchmark)](https://pypi.org/project/ssrjson-benchmark/)
+
 The [ssrJSON](https://github.com/Antares0982/ssrjson) benchmark repository.
 
+</div>
+
 ## Benchmark Results
 
-The benchmark results can be found in [results](results). Contributing your benchmark result is welcomed.
+The benchmark results can be found in [website results](https://ikuyo.dev/ssrJSON-benchmark/) or [GitHub results](https://github.com/Nambers/ssrJSON-benchmark/tree/main/results). Contributing your benchmark result is welcomed.
 
 Quick jump for
 
-* [x86-64-v2, SSE4.2](results/SSE4.2)
-* [x86-64-v3, AVX2](results/AVX2)
-* [x86-64-v4, AVX512](results/AVX512)
+* [x86-64-v2, SSE4.2](https://github.com/Nambers/ssrJSON-benchmark/tree/main/results/SSE4.2)
+* [x86-64-v3, AVX2](https://github.com/Nambers/ssrJSON-benchmark/tree/main/results/AVX2)
+* [x86-64-v4, AVX512](https://github.com/Nambers/ssrJSON-benchmark/tree/main/results/AVX512)
 
 ## Usage
 
-To generate a benchmark report, you need to install `ssrJSON` either by fetched [PyPi](https://pypi.org/project/ssrjson/) or built from [source](https://github.com/Antares0982/ssrjson), and toolkit(`ssrjson_benchmark`) from this repo by:
-
-```bash
-python -m build
-pip install dist/*.whl
-```
-
-Then run the benchmark script:
-
 ```bash
-python benchmark.py
+# you may need to install `svglib`, `reportlab` and `py-cpuinfo` as well
+pip install ssrjson-benchmark
+python -m ssrjson_benchmark
 ```
 
 ## Benchmark options
@@ -56,9 +54,6 @@ python benchmark.py
 ## Notes
 
 * This repository conducts benchmarking using json, orjson, and ssrJSON. The `dumps` benchmark produces str objects, comparing three operations: `json.dumps`, `orjson.dumps` followed by decode, and `ssrjson.dumps`. The `dumps_to_bytes` benchmark produces bytes objects, comparing three functions: `json.dumps` followed by encode, `orjson.dumps`, and `ssrjson.dumps_to_bytes`.
-* The ssrJSON built with the `BUILD_BENCHMARK` option includes several additional C functions specifically designed for executing benchmarks. These functions utilize high-precision timing APIs, and within the loop, only the time spent on the actual `PyObject_Call` invocations is measured.
-* When orjson handles non-ASCII strings, if the cache of the `PyUnicodeObject`’s UTF-8 representation does not exist, it invokes the `PyUnicode_AsUTF8AndSize` function to obtain the UTF-8 encoding. This function then caches the UTF-8 representation within the `PyUnicodeObject`. If the same `PyUnicodeObject` undergoes repeated encode-decode operations, subsequent calls after the initial one will execute more quickly due to this caching. However, in real-world production scenarios, it is uncommon to perform JSON encode-decode repeatedly on the exact same string object; even identical strings are unlikely to be the same object instance. To achieve benchmark results that better reflect practical use cases, we employ `ssrjson.run_unicode_accumulate_benchmark` and `benchmark_invalidate_dump_cache` functions, which ensure that new `PyUnicodeObject`s are different for each input every time.
-
+* When orjson handles non-ASCII strings, if the cache of the `PyUnicodeObject`’s UTF-8 representation does not exist, it invokes the `PyUnicode_AsUTF8AndSize` function to obtain the UTF-8 encoding. This function then caches the UTF-8 representation within the `PyUnicodeObject`. If the same `PyUnicodeObject` undergoes repeated encode-decode operations, subsequent calls after the initial one will execute more quickly due to this caching. However, in real-world production scenarios, it is uncommon to perform JSON encode-decode repeatedly on the exact same string object; even identical strings are unlikely to be the same object instance. To achieve benchmark results that better reflect practical use cases, we employ `ssrjson.run_unicode_accumulate_benchmark` and `benchmark_invalidate_dump_cache` functions, which ensure that new `PyUnicodeObject`s are different for each input every time. (ref: [orjson#586](https://github.com/ijl/orjson/issues/586))
 * The performance of JSON encoding is primarily constrained by the speed of writing to the buffer, whereas decoding performance is mainly limited by the frequent invocation of CPython interfaces for object creation. During decoding, both ssrJSON and orjson employ short key caching to reduce the number of object creations, and this caching mechanism is global in both cases. As a result, decoding benchmark tests may not accurately reflect the conditions encountered in real-world production environments.
-
 * The files simple_object.json and simple_object_zh.json do not represent real-world data; they are solely used to compare the performance of the fast path. Therefore, the benchmark results should not be interpreted as indicative of actual performance.

{ssrjson_benchmark-0.0.1a0 → ssrjson_benchmark-0.0.1rc1}/src/ssrjson_benchmark.egg-info/SOURCES.txt

@@ -2,6 +2,7 @@ CMakeLists.txt
 LICENSE
 MANIFEST.in
 README.md
+pyproject.toml
 setup.py
 cmake/XcodeProperty.cmake
 src/benchmark.c
@@ -12,7 +13,6 @@ src/ssrjson_benchmark/template.md
 src/ssrjson_benchmark.egg-info/PKG-INFO
 src/ssrjson_benchmark.egg-info/SOURCES.txt
 src/ssrjson_benchmark.egg-info/dependency_links.txt
-src/ssrjson_benchmark.egg-info/requires.txt
 src/ssrjson_benchmark.egg-info/top_level.txt
 src/ssrjson_benchmark/_files/MotionsQuestionsAnswersQuestions2016.json
 src/ssrjson_benchmark/_files/apache.json

ssrjson_benchmark-0.0.1a0/src/ssrjson_benchmark.egg-info/requires.txt

@@ -1,8 +0,0 @@
-ssrjson
-orjson
-matplotlib
-
-[all]
-svglib
-reportlab
-py-cpuinfo