pycedar 0.2.1__tar.gz → 0.2.2__tar.gz

{pycedar-0.2.1 → pycedar-0.2.2}/CHANGELOG.md

@@ -7,6 +7,41 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.2] - 2026-09-16
+
+### Added
+
+- `benchmarks/bench.py`, which times the operations pycedar is used for so that
+  a performance change can be measured rather than assumed.
+
+### Changed
+
+- `dict.get()`, `set()`, `setdefault()`, `update()` and `get_node()` are roughly
+  twice as fast. They were declared with a fused `str`/`bytes` parameter, and
+  Cython's runtime dispatch for that cost more than the trie operation itself.
+  The parameter is now `object`, which is what `d[key]` already used; the key
+  type is still enforced by the trie underneath, so behaviour is unchanged.
+- Sentinel checks on the lookup paths compare against C constants instead of
+  building a Python tuple of Python ints on every call, which speeds up
+  `d[key]`, `key in d` and the traversals.
+
+  Measured on 20000 random keys, CPython 3.13, nanoseconds per operation:
+
+  | operation | 0.2.1 | 0.2.2 |
+  | --- | --- | --- |
+  | `d.get(key)` | 302 | 135 |
+  | `d.set(key, value)` | 242 | 108 |
+  | `d.update(key, delta)` | 235 | 112 |
+  | `d.setdefault(key)` | 290 | 129 |
+  | `d.get_node(key)` | 348 | 177 |
+  | `d[key]` | 165 | 132 |
+  | `key in d` | 133 | 123 |
+
+### Fixed
+
+- `node.traverse()` compared integers with `is`, which only worked because
+  CPython interns small integers. It now uses `!=`.
+
 ## [0.2.1] - 2026-09-16
 
 ### Added
@@ -131,7 +166,8 @@ records; the corresponding tags were added retroactively.
 
 - Build failure with clang on macOS.
 
-[Unreleased]: https://github.com/akivajp/pycedar/compare/v0.2.1...HEAD
+[Unreleased]: https://github.com/akivajp/pycedar/compare/v0.2.2...HEAD
+[0.2.2]: https://github.com/akivajp/pycedar/compare/v0.2.1...v0.2.2
 [0.2.1]: https://github.com/akivajp/pycedar/compare/v0.2.0...v0.2.1
 [0.2.0]: https://github.com/akivajp/pycedar/compare/v0.1.3...v0.2.0
 [0.1.3]: https://github.com/akivajp/pycedar/compare/v0.1.2...v0.1.3

{pycedar-0.2.1/pycedar.egg-info → pycedar-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pycedar
-Version: 0.2.1
+Version: 0.2.2
 Summary: Python binding of cedar (implementation of efficiently-updatable double-array trie) using Cython
 Home-page: https://github.com/akivajp/pycedar
 Author: Akiva Miura
@@ -378,6 +378,19 @@ $ python setup.py build_ext --inplace
 
 ``./clean.sh`` removes build artifacts.
 
+### Benchmarks
+
+``benchmarks/bench.py`` times the operations pycedar is used for. Run it against
+two builds to check whether a change actually paid off:
+
+```shell
+$ python benchmarks/bench.py --label before
+$ python benchmarks/bench.py --label after
+```
+
+It uses ``rich`` for the table when that is installed, and plain text
+otherwise. ``--help`` lists the knobs.
+
 ## Releasing
 
 The version lives in a single place, [``pycedar/VERSION``](pycedar/VERSION).

{pycedar-0.2.1 → pycedar-0.2.2}/README.ja.md

@@ -337,6 +337,19 @@ $ python setup.py build_ext --inplace
 
 ``./clean.sh`` でビルド生成物を削除できます。
 
+### ベンチマーク
+
+``benchmarks/bench.py`` が主要な操作の実行時間を計測します。変更に効果があった
+かどうかは、2 つのビルドで実行して比較してください。
+
+```shell
+$ python benchmarks/bench.py --label before
+$ python benchmarks/bench.py --label after
+```
+
+``rich`` が入っていれば表形式で、無ければプレーンテキストで出力します。
+指定できる項目は ``--help`` を参照してください。
+
 ## リリース手順
 
 バージョンは [``pycedar/VERSION``](pycedar/VERSION) の 1 箇所のみで管理します。

{pycedar-0.2.1 → pycedar-0.2.2}/README.md

@@ -340,6 +340,19 @@ $ python setup.py build_ext --inplace
 
 ``./clean.sh`` removes build artifacts.
 
+### Benchmarks
+
+``benchmarks/bench.py`` times the operations pycedar is used for. Run it against
+two builds to check whether a change actually paid off:
+
+```shell
+$ python benchmarks/bench.py --label before
+$ python benchmarks/bench.py --label after
+```
+
+It uses ``rich`` for the table when that is installed, and plain text
+otherwise. ``--help`` lists the knobs.
+
 ## Releasing
 
 The version lives in a single place, [``pycedar/VERSION``](pycedar/VERSION).

pycedar-0.2.2/pycedar/VERSION

@@ -0,0 +1 @@
+0.2.2