Skip to content

G3.4: Measure console/connect_all phase timing inside MaaBootManager #130

Description

@kat-perez

Parent: #126

Hypothesis

helpers::connect_all + proxy::connect_all_default_consoles may be doing redundant connects or slow connects that account for the perf delta. Without per-phase numbers we can't tell.

Steps

  • Add timing instrumentation in patina_bin/bin/patina_x64.rs::MaaBootManager::execute() around each step (use patina_performance::Measurement or raw boot_services.get_time()).
  • Capture FPDT log, parse with Measure-BootPerf.ps1.
  • Compare per-phase times against C BDS phase times from prior LKG.
  • If connect_all dominates, consider scope reduction (only connect required handles for boot, not exhaustive).

Exit

Per-phase timing data available; bottleneck phase identified; mitigation path documented.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions