Reduce path formatting allocations
This commit is contained in:
@@ -1,7 +1,8 @@
|
||||
# Startup Loading Performance Roadmap
|
||||
|
||||
Status: Stages 1–3 complete; optimization has not started. Findings and
|
||||
reproduction commands are in [startup-benchmark.md](startup-benchmark.md).
|
||||
Status: Stages 1–3 complete; Stage 4 is in progress with the first optimization
|
||||
retained. Findings and reproduction commands are in
|
||||
[startup-benchmark.md](startup-benchmark.md).
|
||||
|
||||
Audience: ConfigKit maintainers implementing and reviewing this work.
|
||||
|
||||
@@ -121,7 +122,10 @@ finding and recommend whether further investigation is justified.
|
||||
|
||||
### 4. Implement and measure focused changes
|
||||
|
||||
Status: Not started.
|
||||
Status: In progress. `Path.String` buffer sizing is retained after fresh
|
||||
construction, consumer, inspection, and profile comparisons. See the
|
||||
[focused experiment](startup-benchmark.md#focused-experiment-pre-size-pathstring).
|
||||
The next candidate is duplicate final-tree traversal during metadata finalization.
|
||||
|
||||
1. Implement the selected internal change while preserving the supported API
|
||||
and established behavior. Audit any reduced copying or reused data for
|
||||
|
||||
Reference in New Issue
Block a user