Skip to content

Cache message class ancestry and handler declarations for dispatch - #103

Closed
trissim wants to merge 2 commits into
mainfrom
perf/native-declared-dispatch-supply-20261007
Closed

trissim wants to merge 2 commits into
mainfrom
perf/native-declared-dispatch-supply-20261007

Conversation

@trissim

@trissim trissim commented Oct 7, 2026 •

Copy link
Copy Markdown

Abandoned Codex attempt. Closed without merging.

Message dispatch rebuilt the class declaration views and the filtered message ancestry on every delivery. The change stores both on the class, in message.py and message_pump.py, and recomputes them when the class's method resolution order changes. Handler methods are still read from the live class dictionaries. Tests are added to test_on.py.

@trissim

trissim commented Oct 7, 2026

Copy link
Copy Markdown
Author

The related controls and real private fanout App pass, but this declaration-view supply does not establish a performance gain. Dispatch self-time per recorded generator call was 4.49us versus 4.24us in the earlier profile, with differing workload counts; new supply methods add about 58ms. Closing rather than shipping extra retained declaration state as a speed fix. Tested source remains on this branch. Original output and profile comparison: /home/ts/.cache/agent-scratch/native-declared-dispatch-20261007. No package/public/provider operations.

@trissim trissim closed this Oct 7, 2026
@trissim trissim changed the title Supply native dispatch ancestry through its class owners Cache message class ancestry and handler declarations for dispatch Oct 11, 2026
@trissim
trissim deleted the perf/native-declared-dispatch-supply-20261007 branch October 11, 2026 20:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant