Repository navigation
Establish paired editor performance baseline without runtime changes - #16
Merged
Merged
Conversation
This was referenced Nov 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a manual Python/pywinauto/psutil benchmark outside the application, with pinned test-only dependencies, generated workloads, isolated settings, warmups/rotated order, raw samples, medians and spread.
Record a seven-run comparison of the public x64 releases 1029 and 1040. Loading and private memory are close. The 1 MiB-line scroll/repaint result is slower in the current release and is explicitly flagged for investigation rather than declared equivalent. No optimization or runtime application changes are included.
Validation: the benchmark completed all three workloads/modes; both public candidate archives passed checksum/metadata verification and all 94 pytest cases before measurement. Normal CI remains correctness-based; benchmark measurements are manual and not noisy pass/fail gates. Fixes #14.