docs(benchmarking): Record GLM 5.2 corpus run#423
Merged
Conversation
Add the OpenRouter GLM 5.2 high Sentry corpus benchmark result and the matching docs readout. Note the no-finding JSON parser issue and the repaired shard handling so reviewers can distinguish benchmark performance from run cleanup. Co-Authored-By: GPT-5 Codex <noreply@anthropic.com>
dcramer
force-pushed
the
docs/glm-52-benchmark
branch
from
7fa7449 to
2a6d84d
Compare
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
1 participant
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.
Record the OpenRouter GLM 5.2 high Sentry corpus benchmark result in the docs benchmark data and add the matching readout. The row captures the validated high-effort run after failed shard repair, including the lower recall and the run cleanup needed to make the artifacts comparable.
Benchmark Result
Add the traced GLM 5.2 result JSON with 15 of 86 known corpus findings found, 18 emitted findings, and the validated token, cost, and timing summaries.
Run Notes
Document the GLM 5.2 no-finding parser issue, the combined-clean shard artifacts, and the
seer_rpc.pylower-parallelism repair so the result is interpreted as benchmark data with an operational caveat.