https://github.com/lightsofapollo/sqs-playground
Totally useless repo only for my personal testing
https://github.com/lightsofapollo/sqs-playground
Last synced: 8 months ago
JSON representation
Totally useless repo only for my personal testing
- Host: GitHub
- URL: https://github.com/lightsofapollo/sqs-playground
- Owner: lightsofapollo
- Created: 2015-05-12T03:39:55.000Z (about 11 years ago)
- Default Branch: master
- Last Pushed: 2015-05-12T05:24:55.000Z (about 11 years ago)
- Last Synced: 2024-12-27T15:12:40.420Z (over 1 year ago)
- Language: JavaScript
- Size: 137 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# SQS/SNS Playground...
The idea here was to see how easy it was to use sqs/sns together and how fast
I could use them in a few different situations. In particular the workload I am
targeting takes 30-200s total so waiting a huge amount of time to start that work
is a non starter.
The [code](/perf.js) is not particularly smart it creates a sqs queue
dynamically and links it up to a sns topic (also created dynamically) creating a
"fanout" model (note yes you can have infinity sqs queues!) then continues on
sending and receiving messages in parallel (note no http optimization was done here).
Each message contains a json encoded time that gets compared to the current time
when we decode the message...
## Results
Taken over 2k messages.
| Region | Median Round Trip* |
| -------| -------------------|
| same region | 0.33s |
| us-east-1 | 0.757s |
| my laptop | 0.541s |
*Note that the round trip _includes_ the time to send the message simulating the use case of
parallel sender/recievers (YMMV).