This repository was archived by the owner on Nov 21, 2026. It is now read-only.
Repository navigation
benchmarks: native time-series arms use the engine's default SHARDS (#241) - #242
Merged
Merged
Conversation
…DS, not a fixed 4 that flatters ArcadeDB (#241) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ubz3m6QXHESerCkehC1qgi
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Closes #241.
The native time-series arms (embedded and served) no longer fix
SHARDS 4: the clause is left out, so the engine derives the shard count from its async workers, which is what upstream names (ArcadeData#9166 and the time-series docs). A round 2 best-practice probe measured the fixed 4 at 0.505 ms against 1.007 ms for the default 11 on the 12 h hourly aggregate (ratio of medians 1.99, five runs per arm, JDK 25, official 26.10.1 jars, same answers), so the default is the setting that does not flatter ArcadeDB.TS_SHARDS=4reproduces the old arm. Rows recordts_shards(0 for the default) andts_shard_count_effective(read fromschema:types). PROTOCOL.md and CAMPAIGN.md row 54 are updated, and the tests assert the DDL has noSHARDSclause by default, that the env var brings it back, and that the readback parses the engine report. I also created a type without the clause through the 26.10.1 wheel to confirm the DDL parses and the report carriesshardCount(3 under cores 4-7).Not verified: JDK 21, and the effect on mini (the mini rows are the measurement). The time-series stage has not started on mini, so no rows are split.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Ubz3m6QXHESerCkehC1qgi