Replies: 2 comments
-
Why were you expecting this? They both just go and use curl to hit the server, behind the scenes. It is largely no different, especially with the super small response bodies from sqs. The difference could be down to the async aws having more files to load for the first time compared to the official sdk. Are you able to compare performance of the 2nd request, reusing the same client instance? |
Beta Was this translation helpful? Give feedback.
-
Before digging deeper into the code I was thinking that if I didn't use the result the message would have been sent as 'fire and forget', so I was surprised about the benchmarks. Since my use case was to send a message for every http request made to my backend ∼50ms were too much (I don't have the possibility to reuse the same connection), so I moved away from SQS and therefore I cannot do further benchmarks on it. |
Beta Was this translation helpful? Give feedback.
-
Hi, I run a few tests with the async-sqs library and the official aws sdk, I was expecting the async library to be much faster but sending a message I get an average of 65ms using the async lib (without using the result) and 55ms using the official lib (sync, getting the result), the code is the same, only the SQSClient import is different:
If someone knows if I'm doing something wrong I would appreciate a lot.
Beta Was this translation helpful? Give feedback.
All reactions