--
>>>>>>>>>> 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+...@googlegroups.com.
To post to this group, send email to akka...@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
Hi,Instead of Http.request, you should use the Flow returned by Http.superPool() (see http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0-RC3/scala/http/client-side/request-level.html). That flattens out the Futures and you get responses instead. That also makes Balance actually aware of response times.OTOH I don't think performance wise akka-http is currently up to the task of being a balancer.
On Wed, May 27, 2015 at 2:01 PM, Endre Varga <endre...@typesafe.com> wrote:Hi,Instead of Http.request, you should use the Flow returned by Http.superPool() (see http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0-RC3/scala/http/client-side/request-level.html). That flattens out the Futures and you get responses instead. That also makes Balance actually aware of response times.OTOH I don't think performance wise akka-http is currently up to the task of being a balancer.…at the moment.
You received this message because you are subscribed to a topic in the Google Groups "Akka User List" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/akka-user/_wd1vl0mzfE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to akka-user+...@googlegroups.com.
Here it is https://github.com/zergood/akka-http-loadbalancer.git.Actualy this implemetation is not good, because I've relized that with Http().superFlow I miss request-response ordering.
Some requests get wrong responses, it is not so important for this implementation, because all responses are the same.How can I repair request-response ordering? I think about mapping request to some id, and store all unhandled requests before I get (response, id) from server, another variant is passing RequestContext to superFlow. Are there another ways how to do this?P.S in this implementation balancer performance ~900r/s. Single local http server performance is ~4800r/s.