eric/promptkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Mark the ConfigKit performance request complete

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-08 23:50:38 +00:00
parent eb830bb613
commit 481e2d494c
1 changed files with 13 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
docs/roadmap/performance.md
View File

@@ -1,6 +1,7 @@
# Computational Efficiency Improvements
Status: Accepted scope following review; implementation has not started.
Status: Accepted scope following review. The ConfigKit request (item 1) is
complete; local performance implementation has not started.
## Purpose
@@ -45,25 +46,16 @@ their benefits still need measurement.
### 1. Submit A ConfigKit Performance Feature Request
Submit an appropriate feature request for ConfigKit's consideration, describing
Promptkit's downstream configuration-construction workload and the measured
allocation cost. Include the fixture shape, selected ConfigKit version,
benchmark method, and allocation-profile evidence so upstream maintainers can
reproduce and assess it. The existing
[construction benchmark](../../internal/configuration/benchmark_test.go) and
[configuration adapter](../../internal/configuration/load.go) provide the
downstream context.
Completed on 2026-10-08. The request is recorded in ConfigKit's
`docs/roadmap/promptkit-performance-request.md`, committed as `d53021e`.
It includes the downstream fixture, dependency and toolchain versions,
repeated benchmark results, reproduction commands, and allocation-profile
observations, while preserving existing configuration and inspection semantics.
Request more efficient construction while retaining the source composition,
resolution, final-value handoff, and operator-inspection capabilities Promptkit
uses. Explain why libraries that build multiple engines or load large catalogs
benefit, and distinguish startup cost from ordinary prompt execution.
Leave acceptance, internal design, and implementation to ConfigKit. Submission
and upstream consideration are the local outcome for this item; adoption of a
future upstream improvement can be assessed when one is available. Promptkit's
other improvements can proceed independently. Reimplementing ConfigKit's loader
or bypassing its configuration ownership is outside this scope.
Acceptance, design, and implementation remain with ConfigKit. Upstream
improvements will become available through a later ConfigKit dependency upgrade;
no further Promptkit-specific work remains for this item at present. Local
performance improvements can proceed independently.
### 2. Avoid Response Copies In Basic Validation
@@ -162,8 +154,8 @@ allocation costs. Follow with request encoding and identity-only inspection
Keep prepared-state consolidation (item 6) conditional on measured savings and
a clear ownership analysis; it has the greatest risk of weakening isolation or
concurrency behavior. The ConfigKit request (item 1) can proceed independently
and does not block local improvements. This order is a recommendation, not a
concurrency behavior. The ConfigKit request (item 1) is complete and does not
block local improvements. This order is a recommendation, not a
dependency between otherwise independent changes.
## Benchmarking And Verification