Hi Viktor, Maybe you could abstract the transport API and create multiple implementations, with both Netty and Aeron, Aeron might not be as fast as you think, some performance benchmark on different transports and keep a updated score table to keep the user informed on what transport works best under specific scenarios like:
- Many small messages (high frequency with low latency) - Standard amount of messages with standard size (amount of messages and size TBD) - And for large messages. So different transports and/or configuration of them might provide a better performance for different scenarios. My main concern is that nobody seems to be concerned AFAIK with this subject nor aware on how slow the current remote transport is hence my post subject "Akka remote communication roadmap?", at least it is slow for my application and its configuration. Best regards, Guido. On Wednesday, October 14, 2015 at 1:49:04 PM UTC+1, √ wrote: > > For extremely low latency we'd want to use a transport like Aeron. > > On Wed, Oct 14, 2015 at 1:34 PM, Guido Medina <oxy...@gmail.com > <javascript:>> wrote: > >> Very nice, I wasn't aware of it, IMHO it needs something like that as >> proper remote communication is the foundation for distributed >> micro-services, our application is a FOREX trading application and we might >> eventually move to high-frequency trading, it is in production and for what >> we do at the moment the times are within the OK parameters, but for high >> frequency trading it will be a show stopper, I do believe Akka remote, >> cluster and other remote related extensions will play a nice role in the >> future of financial services, or maybe I'm just too excited with Akka and >> getting ahead of myself, who knows ;-) >> >> Thank you very much for that info, >> >> Guido. >> >> >> On Wednesday, October 14, 2015 at 12:27:46 PM UTC+1, Andrey Kuznetsov >> wrote: >>> >>> Did you see this? >>> https://github.com/typesafehub/netty-reactive-streams/blob/master/pom.xml >>> I think it's a first step of migration to streams. It already depends on >>> Netty 4. >>> >>> On Wednesday, October 14, 2015 at 12:22:33 PM UTC+3, Guido Medina wrote: >>>> >>>> Hi, >>>> >>>> I created a similar post some time ago but the circumstances were a bit >>>> different, the project I'm working at the moment has the requirement of >>>> processing messages within 5ms, and I chose Akka remote to do this job, >>>> the >>>> project also requires to be distributed so again, Akka remote with >>>> clustering was the clear candidate, I have done lots of research and have >>>> done the following: >>>> >>>> - Properly configured Netty TCP client and server pools. >>>> - Properly configured serialization using Kryo. >>>> - I have created small, immutable and concise Java classes for >>>> sending messages between remote actors. >>>> - I have configured properly Akka remote thread pools. >>>> >>>> And it doesn't matter what I do, I still get a high time with the 1st >>>> few messages, I cannot make my application send messages in less than 2ms >>>> to 5ms after initial warm up, sometimes it takes even more, I would be >>>> curious about low latency applications out there that use Akka remote, the >>>> state of Akka remote IMHO is "out-dated?" >>>> >>>> I think it needs more attention, I'm quite sure the community >>>> appreciates so many features you guys are releasing but I think remote >>>> communication is not only an important but crucial aspect of Akka. >>>> >>>> In my old post someone mentioned there would be an Akka remote >>>> rewritten using Akka streams, it has been some reasonable time now to >>>> start >>>> thinking about, Akka 2.4, Akka HTTP 1.0 are already released and still >>>> Akka >>>> remote is using Netty 3, a shorter time alternative would be to just >>>> migrate Akka remote to Netty 4 which someone has proven already it faster >>>> and consistent for Akka. >>>> >>>> >>>> Best regards, >>>> >>>> Guido. >>>> >>> -- >> >>>>>>>>>> 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 <javascript:>. >> To post to this group, send email to akka...@googlegroups.com >> <javascript:>. >> Visit this group at http://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Cheers, > √ > -- >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
