To be clear, 95th percentile and down are as low as before so wondering if this is a new connection closing penalty being paid or if the actor system needs to be tuned differently now...
On Thursday, October 12, 2017 at 4:31:14 PM UTC-4, Gary Malouf wrote: > > We have a web service that we just finished migrating from spray 1.3 to > Akka-Http 10.0.9. While in most cases it is performing well, we are seeing > terrible 99th percentile latencies 300-450ms range) starting from a very > low request rate (10/second) on an ec2 m3.large. > > Our service does not do anything complicated - it does a few Map lookups > and returns a response to a request. In spray, even 99th percentile > latencies were on the order of 1-3 ms, so we are definitely concerned. > Connections as with many pixel-type servers are short-lived -> we actually > pass the Connection: Close header intentionally in our responses. > > Is there any obvious tuning that should be done on the server > configuration that others have found? > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
