Hi Konrad, Actually we are using externalizable where we write to the stream directly. We have used protobuf and we had issues with creating the java object for protobuf which took a lot of memory and so we decide to go with externalizable.
Good point about the way the tcp connection is being used. I'll look at akka.io and see if we can fit that into our design. I won't say I have't thought about that but it appeared to be more work than it was worth. Thanks for your response. -Moiz On Sunday, 22 February 2015 12:18:55 UTC-8, Akka Team wrote: > > Hi Moiz, > actor messaging is *not* designed for very large messages - you should use > akka.io and a dedicated tcp socket for this. > With actor messaging all messages share one tcp connection, thus you're > blocking all messages to go through until the large message has been sent. > > Also, exacly as Jim highlights - you *must not* use java serialization in > any scenario that cares about latencies - java serialization is well known > to be very slow, and we only include it to get PoC and examples running > easily and "out of the box". You should pick a proper serialization format > that suits your needs > such as protocol buffers, cap'n proto or kyro (there's a multitude of > other serialization formats - including simple binary encoding for > example), but you have to pick the one which suits your specific > application needs the best (in terms of protocol evolution, performance and > ease of use). > > We discussed multiple serialization formats on akka-user previously, > you'll find some great discussions by looking through the archives. > If you have any more questions please do shoot follow up questions here, > we'll try to help :-) > > -- Konrad > > On Tue, Feb 17, 2015 at 8:56 AM, Jim Hazen <[email protected] > <javascript:>> wrote: > >> You might want to try a custom serializer. Bottom of this page. I'd be >> interested to know how well they work. Never used em, sorta curious. >> >> http://doc.akka.io/docs/akka/2.3.9/scala/serialization.html >> >> There is also a remoting SPI, but I don't know of any alternate >> implementations. >> >> -- >> >>>>>>>>>> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Akka Team > Typesafe - The software stack for applications that scale > Blog: letitcrash.com > Twitter: @akkateam > -- >>>>>>>>>> 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.
