I rewrite it with akka-io-netty ,it has the same api as the akka-io,and then redo the transport based on it.but my company asked me to delete it from the github.so sorry.and the link below is unmatained and we are not using it in production any more. and I think for the really HT,you could do the things like: 1,reduce context switch 2,reduce gc pressure 3,quick serialization 4,don't using tcp 5,don't using akka remote directly
If I was you ,I would start a dedicated endpoint for the exchange ,which may be based on Aeron or Netty4 with UDT.only by using akka-stream and netty4 will not make it works here I think,5 ms,need some special work. > -- >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
