You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Benchmarks: the served ArcadeDB arms leave -Xms unset, like the embedded arms since #429 #455
#429 took -Xms off the embedded ArcadeDB arms of the benchmarks only, so the two deployments no longer run one JVM configuration: the served arms still pass ARCADEDB_OPTS_MEMORY=-Xms{heap} -Xmx{heap}. The embedded-versus-served comparison isolates transport only when the JVM is the same (DECISIONS #46, #54, #114, #159), so one side has to move, and the served side is the one that matches ArcadeDB's maintainers' Docker guidance (ArcadeData#9167, arcadedb-docs "JVM settings in a fixed memory budget": no -Xms in a container).
Scope: the served ArcadeDB arms pass only -Xmx{heap} (G1 and the 50% heap budget stay), the docs and the generated page sentences say so, an untimed memory check of a served 26.10.2 container records pinned versus unset, and the other JVM engines are verified against their vendors' current docs and kept (Neo4j and Elasticsearch pin by their vendors' recommendation, QuestDB sets no heap). The comparator subset is unaffected: the ArcadeDB arms run in the Nov 5-12 pass.
Activity
Benchmarks: the served ArcadeDB arms leave -Xms unset, like the embed…
PROTOCOL: what each JVM engine's vendor says to size beyond the heap,…
Benchmarks: the served ArcadeDB arms leave -Xms unset, like the embed…
PROTOCOL: what each JVM engine's vendor says to size beyond the heap,…
Benchmarks: the served ArcadeDB arms leave -Xms unset, like the embed…