pyronova: bump to v2.4.2#684
Open
ddxd wants to merge 2 commits into
Open
Conversation
- PYRONOVA_WORKERS now controls TPC thread count (was wrongly using PYRONOVA_IO_WORKERS which is semantically the Tokio async IO pool) - Launcher sets PYRONOVA_WORKERS=sched_getaffinity() so all logical CPUs are used (64 on Threadripper 32C/64T, vs 32 physical in v2.3.1) - Per-interpreter pre-serialized bytes cache for json/json-comp routes (256-entry cap, no lock contention between sub-interpreters) - TLS multi-port fix: extra_tls_ports no longer applies TLS acceptor to the plain HTTP main port Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The pyronova repo moved from github.com/moomoo-tech to github.com/leocaolab. GitHub redirects still resolve, but pin the canonical URL so the Arena CI build and the framework metadata both reference the live org directly.
Owner
|
/benchmark -f pyronova |
Contributor
|
👋 |
Contributor
Benchmark ResultsFramework:
Full log |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Engine (v2.4.2 — leocaolab/pyronova)
PYRONOVA_WORKERScontrols TPC thread count — previously the TPC thread count was driven byPYRONOVA_IO_WORKERS(a Tokio-level knob), whilePYRONOVA_WORKERSwas silently ignored in TPC mode. NowPYRONOVA_WORKERSis the correct lever, keeping semantics consistent with the non-TPC path.too_many_argumentsallows on TPC accept functions;get_first()instead ofget(0).Launcher
PYRONOVA_WORKERS = sched_getaffinity()so all logical CPUs visible to the container are used. On a Threadripper 32C/64T host this is 64 threads vs. 32 (physical-core auto-detect in v2.3.1). Removes thePYRONOVA_IO_WORKERSoverride that was incorrectly controlling TPC thread count.App
/json/{count}and/json-comp/{count}routes. Each sub-interpreter maintains its owndict[tuple, bytes](max 256 entries) — no lock contention, no Response object reuse. Cache stores compactjson.dumps(..., separators=(",", ":"))bytes; each cache hit wraps in a freshResponse().extra_tls_portsno longer accidentally applied the TLS acceptor to the plain-HTTP main port.Test plan
cargo clippycleancargo testpasses locally (52/52)v2.4.2tag/json/10returns correct JSON payload🤖 Generated with Claude Code