One of the building blocks of TCP is "slow start" and "slow start restart" ....
https://hpbn.co/building-blocks-of-tcp/#slow-start In particular for bursty applications "slow start restart" could be hampering the performance of an Akka app by not using the full bandwidth available at the time of the 'bursty' traffic. (I do not have any evidence that this is an issue for my scenario, it's still in the design stage.) 1. Anyone got links to case studies of this effect in their app? (Either related to Akka TCP or Akka in general) 2. Are there any settings or machinery in Akka under the hood that directly effect this "slow start restart"? I'm trying to determine is this a known handled thing or something we know about and accept or something we don't need to worry about because I've misunderstood it? Much thanks for reading! Alan. -- >>>>>>>>>> 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.
