-
Notifications
You must be signed in to change notification settings - Fork 48
Websockets #1528
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
base: development
Are you sure you want to change the base?
Websockets #1528
Conversation
k6 load testing comparison.
Legend: Avg - Average Response Time, Max - Maximum Response Time, 90 - 90th Percentile, 95 - 95th Percentile |
config/config.testnet.yaml
Outdated
collectionPropertiesFromGateway: false | ||
features: | ||
websocketSubscription: | ||
enabled: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
make them disabled by default maybe? can be left as a TODO before PR's merging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
# Conflicts: # config/config.mainnet.yaml
Reasoning
Proposed Changes
transactions
,blocks
andstats
How to test
Example:
client1: subscribeTransactions with payload {from=0, size=10}, subscribeBlocks with payload {from=0, size=2}
client2: subscribeTransactions with payload {from=0, size=2}, subscribeBlocks with payload {from=0, size=5}, subscribeStats
on each client you should only receive data the same as you would request that specific endpoint with those specific parameters and the server
must
perform only 1 computation per eachroom
at a specific interval regardless of the number of clients in that room -> a room is unique by topic and payload (filter parameters)