Runtime Profiles and Costs

Match enabled features and allocation lifecycle to your workload. These v2 studies record the source revisions, hardware, configuration, raw samples, and known costs.

• Runtime profiles: individual options, unused-feature overhead, and recipes for comments, articles, documentation, and MDX.
• Release performance assessment: accepted costs and release scope.
• Full ARM suites: 207 cases across parser, rendering, and full-processing stages.
• Optional writing features: marked text, inline notes, and reference-policy costs.

Unused enabled extensions can add work. Fresh calls include setup and teardown; reused lifecycles retain allocations where supported. No native-core result by itself measures Node request latency or an entire site's build time.

Native comparisons use their own matched profiles and output checks. Historical v1 measurements remain in v1 history and are not v2 results.