-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check performance of guarded delegate calls #20
Labels
Performance
Performance implications
Comments
Some preliminary results from putting guarded delegate behind a config. Event throughput: grouped by number of events:
Subscribe cost: grouped by complexity:
E2E amortized cost:
|
Wowsers, so the guarded delegate calls seem to be most of the cost. This matches what I saw in some preliminary testing. We should definitely add a flag to control them in |
CC @dlew |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Requires #17 to be done to add some benchmarking for comparison. If it's expensive, consider putting behind a config
The text was updated successfully, but these errors were encountered: