[akka-user] Akka and Lagom

Hi, As a Scala/Akka novice, was wondering if the new Lagom Scala coding paradigm is going to reflect some of the Akka API. in other words, to what degree will we need to redesign Akka projects to start using Lagom Services. I have taken a look at some of the Lagom Java examples out there, and

Re: [akka-user] Re: Is it possible to increase the number of serialization threads?

Hi Guido. After implementing your suggestions I'm realizing that maybe my particular case is a bit peculiar, I'm interested in a benchmark involving 2 hosts. I'm getting around 500.000 transactions per second (echo of array of 48 bytes), which is not a so bad number. Increasing the number of

Re: [akka-user] Is it possible to increase the number of serialization threads?

Hi Viktor. I'm using basic (binary) serialization of basic Java types (int, String (UTF), long, arrays of basic types, etc...). The overhead is that depending of internal values there is no send to serialize some members and other not. If you merge your functional logic with the serialization

Re: [akka-user] Is it possible to increase the number of serialization threads?

Hi Eduardo, Perhaps I misunderstood, what serialization format are you emitting in your readObject/writeObject? What overhead are you observing compared to using a custom Serializer? On Sat, Jul 2, 2016 at 10:02 PM, Eduardo Fernandes wrote: > Hi. > > If you have

Re: [akka-user] Is it possible to increase the number of serialization threads?

Hi. If you have writeObject/readObject defined in your class the Java plain serialization will invoke those methods. In my case all my internal members and class references are also serialized using the very same technique. So this is equivalent to technologies like kryo and similars since there

Re: [akka-user] Is it possible to increase the number of serialization threads?

I'm not sure I understand why write/readObject special methods would necessarily be faster? Most of the waste of Java Serialization is its envelopes and using class names etc. On Sat, Jul 2, 2016 at 1:14 AM, Eduardo Fernandes wrote: > Hi. > > I'm using Akka 2.3.13, Java

[akka-user] How to find Oldest node in Akka Cluster Singleton

Hi, In akka cluster singleton how to find "Oldest" node details. Regards, Rajesh -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the archives:

Re: [akka-user] Re: Is it possible to increase the number of serialization threads?

Hi. Many thanks for your suggestions. I will try and let you know. Thanks again for your time. > El 2 jul 2016, a las 13:35, Guido Medina escribió: > > The following might also be helpful: > > > akka.remote { > > #log-remote-lifecycle-events = off > > netty.tcp

[akka-user] Re: Is it possible to increase the number of serialization threads?

The following might also be helpful: akka.remote { #log-remote-lifecycle-events = off netty.tcp { #port = 0 server-socket-worker-pool { pool-size-min = 4 pool-size-factor = 1 pool-size-max = 8 } client-socket-worker-pool { pool-size-min = 4

[akka-user] Re: Is it possible to increase the number of serialization threads?

Didn't read the serialization part, must be that I need my coffee, Kryo is very well optimized, you don't know if is going to help until you test it. Kryo also also has a pool of serializers that are ready to be used and can be improved if you declared the classes you are serializing. On

[akka-user] Akk Cluster Singletion - Oldest node down message

Hi, In Akka Cluster Singleton how worker(younger) node receive a message when Cluster Singleton node(Oldest) was down ? In Akka *younger* node I am seeing below WARN message *[WARN] [07/02/2016 00:32:55.720] [ClusterSystem-akka.actor.default-dispatcher-2]

[akka-user] Re: Is it possible to increase the number of serialization threads?

Try the following, these values work great, you can try higher but I don't think it is going to help because the most of the bottleneck is because of design, a problem related with how akka-remote is designed around Netty, but that will change soon: https://github.com/akka/akka-meta/issues/22

[akka-user] PersistenceQuery: Materialize view to datastore - When should the query stream be stopped?

Talking about the pattern in the subject : I can't find a clean way of managing the lifecycle of persistence query streams that save persisted events to a read datastore