Skip to content

docs: limits of the native build, garbage collector row, migration steps - #84

Merged
tae898 merged 1 commit into
mainfrom
docs-native-limits-migration
Oct 26, 2026
Merged

tae898 merged 1 commit into
mainfrom
docs-native-limits-migration

Conversation

@tae898

@tae898 tae898 commented Oct 26, 2026 •

Copy link
Copy Markdown
Collaborator

Docs-only follow-up of the native production audit. It does not touch the glibc, Python 3.15 or platform statements of #83; the hunks are in other sections, so the two merge without conflict, but merge #83 first (see the last paragraph).

  • Install page: a new section, Limits of the native build. It lists the serial garbage collector (the build log of run 40238118922 says Garbage collector: Serial GC; G1 is Oracle GraalVM only), the 50% default heap limit, the missing Java objects and JVM options, the Windows console log that is off by default, the engine modules left out, and the platforms without a wheel.
  • Which-package table: a Garbage collector row (native serial, JVM G1 by default) next to the Memory row.
  • Which-package, Old names: three migration steps from arcadedb-embedded and arcadedb-embedded-native (uninstall, install the new name, change the import), which the page did not have.

Not rendered locally (no Antora build); the xrefs use the anchors that already exist (native-heap, jvm-options, what-is-included) and requirements, which #83 adds. Until #83 merges the <<requirements>> link in the platforms bullet is unresolved, so merge #83 first.

🤖 Generated with Claude Code

Adds a Limits of the native build section to the install page (serial GC, 50% heap, no Java objects, Windows console log off, engine modules left out, unsupported platforms), a garbage collector row to the which-package table, and three migration steps from arcadedb-embedded and arcadedb-embedded-native.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
@tae898
tae898 merged commit 4522d4c into main Oct 26, 2026
@tae898
tae898 deleted the docs-native-limits-migration branch October 26, 2026 02:29
tae898 added a commit that referenced this pull request Oct 26, 2026
…est's data names

The old-name check failed on main since #84 (the three steps of "Migrate from the old names" in which-package.adoc must name the
old packages; docs-only changes skip the test run that would have shown it) and on the new tests/test_release_name_guards.py (a guard
test needs another distribution name as data).

The migration steps are allowed by one phrase each (pip uninstall, "if you used", "both become"), not by the whole page. The test
names the other distribution in two constants that carry the allow-old-name marker. The check itself is not weakened: any other line
that names the old package still fails.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant