Skip to content

Evaluate Native AOT and trimming for smaller, faster standalone releases #26

Open

Description

@Anheledir

Priority: P2 · Triage: 2026-10-26

Use measured startup/size findings to assess publishing alternatives; improvements are not yet proven.

Depends on measurement results in #25.

Acceptance

  • Compare current bundles, trimming and Native AOT for size, startup and extraction.
  • Audit Spectre/reflection/serialization, QRCoder, resources and native credential APIs; document compatibility warnings.
  • Verify supported runtime builds, native CLI/hooks/install/update/rollback and offline licenses; record go/no-go and fallback. A framework-dependent alternative must document its .NET prerequisite.

Related: #10.

Activity

  1. added
    enhancementNew feature or request
    P2Follow-up: acceptance, robustness and integrations
    on Oct 26, 2026
  2. Anheledir commented on Oct 26, 2026

    @Anheledir
    OwnerAuthor

    Inputs from #25 / #59: the local Linux self-contained executable is 76.6 MB; CLI/Core assemblies are only ~563 KB/~220 KB. Managed bundle compression reduced the executable to 40.6 MB but added roughly 60–95 ms to measured startup and slightly increased gzip bytes (33.16 → 33.40 MB), so it remains disabled. Native benchmark workflow now compares baseline/candidate on Windows/Linux/macOS with isolated extraction caches and a conservative regression budget. This provides the measurement harness for AOT/trimming experiments.

    Bare version uses a minimal bootstrap; install/update probes deliberately use --version --no-interactive to initialize the full command path. Preserve that distinction and all native credential/offline resource/installer/helper/rollback coverage when experimenting with trimming or AOT. Report and local raw measurements: https://github.com/Anheledir/SidePulse.NET/blob/main/docs/performance/2026-10-26-startup.md .

  3. Anheledir commented on Oct 26, 2026

    @Anheledir
    OwnerAuthor

    Investigation and reproducible native CI are in #62. Local linux-x64 results: unrestricted trim 18.05 MB and Native AOT 13.73 MB both fail full command initialization despite a working bare version probe. Retained-metadata/partial-trim JIT prototype is 23.13 MB and passes lifecycle smoke but starts slower (~399 ms Home). Partial trim + ReadyToRun is 39.46 MB (16.98 MB gzip), ~76 ms warm Home, with all seven local smokes passing. Strict clean analysis still exposes JSON/CLI compatibility diagnostics; production publishing and warning policy remain unchanged.

    New delivery tasks: #60 (P1 typed/source-generated JSON contracts, shared with library/schema work) and #61 (P2 trimming/AOT-safe command metadata). #58 execution order is updated. Native investigation: https://github.com/Anheledir/SidePulse.NET/actions/runs/40321721979 . Keep this umbrella open through the compatibility fixes and native acceptance; an experimental green job means evidence collection completed, not that broken variants are supported.

  4. Anheledir commented on Oct 26, 2026

    @Anheledir
    OwnerAuthor

    Investigation merged in #62. Native run: https://github.com/Anheledir/SidePulse.NET/actions/runs/40321721979 . All three report archives were downloaded and their SHA-256 digests match GitHub artifact metadata. Five paired launches per mode on each native runner; sizes are executable-only and times are reused bundle-cache medians, not cold OS or physical hardware observations.

    Native platform Full → partial-R2R executable State preview before → after Home before → after
    linux-x64 76.73 → 39.52 MB 114.50 → 65.13 ms 121.31 → 61.19 ms
    osx-arm64 83.17 → 41.38 MB 104.39 → 52.39 ms 98.46 → 59.97 ms
    win-x64 76.71 → 36.89 MB 199.87 → 116.38 ms Not measured (real console/ConPTY needed)

    On every native platform, the full baseline and diagnostic partial/partial-R2R candidates pass the existing CLI, native vault, docs/licenses, installation/PATH/uninstall, update/rollback and provider smokes (Windows PTY is explicitly skipped by the existing terminal smoke). Raw trim and AOT compile but fail full command startup; strict partial builds fail JSON analysis. A successful experimental workflow means these outcomes were recorded, not that every candidate is supported.

    Decision: retain supported release settings and strict warnings. #60 (P1 typed/source-generated JSON) and #61 (P2 CLI metadata) must be resolved before promoting a smaller candidate. #26 remains open for those fixes and remaining target/hardware acceptance. Reproduction/raw local evidence: https://github.com/Anheledir/SidePulse.NET/blob/main/docs/performance/2026-10-26-deployment.md .

  5. Anheledir commented on Oct 26, 2026

    @Anheledir
    OwnerAuthor

    JSON enablement #60 is merged in #63 and closed. Reflection fallback is disabled in the CLI; 146 .NET tests and 22 baseline JSON/error comparisons pass on native Windows/Linux/macOS. Final deployment run https://github.com/Anheledir/SidePulse.NET/actions/runs/40327765391 confirms no application JSON IL2026/IL3050 diagnostics. The smaller diagnostic ReadyToRun candidates pass lifecycle/native-vault smoke; strict promotion is still gated only by the Spectre/CLI work in #61. Supported release trimming/AOT settings remain unchanged. Contract/compatibility decision: docs/decisions/0004-generated-json-contracts.md.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Follow-up: acceptance, robustness and integrationsenhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions