We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It'd be nice to somehow measure the performance compared to the Netty connector.
The text was updated successfully, but these errors were encountered:
My gut feeling tells me, that Netty would perform better. Where better would mean it would probably produce less garbage.
I also think this would be very hard to measure, because there are a lot of moving parts be involved.
What exactly do you want to measure? I think in terms of speed, there should not be use differences, as probably the most of the time is spent for IO.
Maybe, there is already something in the Aws v2 repository, which they use to test Netty? If so, one could probably built on this.
Sorry, something went wrong.
Switch to ElasticMQ SQS container (matsluni#16)
6da406b
* Switch to ElasticMQ SQS container * Update TestSQS.scala
No branches or pull requests
It'd be nice to somehow measure the performance compared to the Netty connector.
The text was updated successfully, but these errors were encountered: