date:20140823

Re: [akka-user] Actor system unexpected slow down at load?

2014-08-23 Thread Heiko Seeberger

While this is sort of speculative, it looks like you have introduced a 
bottleneck. Maybe you can use a router for your main actor, resulting in 
parallelizing entry work (assuming you have multiple cores and enough threads)?

Heiko

On 23 Aug 2014, at 02:37, Paul Cleary  wrote:

> I have an actor system that is setup using all of the akka defaults.
> 
> Nothing in the system has a lot of latency, we are talking about sub 
> millisecond (20 microsecond) latencies.
> 
> All traffic flows through a single actor to downstream actors.  This "main" 
> actor just forwards the message onto children using a lookup.
> 
> I am doing load testing, and have seen the same trend both on my local, as 
> well as in a server environment.  The "main" actor keeps up superbly up until 
> a certain point.
> 
> I get up to about 1500 requests per second in my load test, which generates a 
> boat load (10s of thousands) of messages against my single actor.
> 
> At that point, all of a sudden the mailbox size gets enormous on my main 
> actor.
> 
> None of the downstream actors are doing anything, so it isn't like some roque 
> actor is chewing up threads.
> 
> The main actor IS making progress, albeit very very very slowly.
> 
> When I did a thread dump, almost all of the dispatcher threads were "waiting" 
> (i.e., parked not doing anything).
> 
> The mailbox size grows into the millions during the test.  The main actor 
> never really catches up, just putt putts along, it doesn't get faster.
> 
> A few other notes:
> 1. I did not max out memory or hit stop the world GC at any point during the 
> test.
> 2. The CPU is very low on the machine, under 50%
> 3. There are no hardcore errors on the main actor, he doesn't restart or 
> anything like that
> 4. I am using Akka 2.2.3
> 
> So, my questions are:
> 1. If the threads aren't busy (they are waiting), why isn't my main actor 
> making faster progress?  Why are the other threads waiting seemingly not 
> doing anything?
> 
> 2. What might cause the system to seemingly "shut down"?
> 
> 
> -- 
> >> 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.

-- 
>>  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.

Re: [akka-user] Actor system unexpected slow down at load?

2014-08-23 Thread Roland Kuhn


23 aug 2014 kl. 02:37 skrev Paul Cleary :

> I have an actor system that is setup using all of the akka defaults.
> 
> Nothing in the system has a lot of latency, we are talking about sub 
> millisecond (20 microsecond) latencies.
> 
> All traffic flows through a single actor to downstream actors.  This "main" 
> actor just forwards the message onto children using a lookup.
> 
> I am doing load testing, and have seen the same trend both on my local, as 
> well as in a server environment.  The "main" actor keeps up superbly up until 
> a certain point.
> 
> I get up to about 1500 requests per second in my load test, which generates a 
> boat load (10s of thousands) of messages against my single actor.
> 
> At that point, all of a sudden the mailbox size gets enormous on my main 
> actor.
> 
> None of the downstream actors are doing anything, so it isn't like some roque 
> actor is chewing up threads.
> 
> The main actor IS making progress, albeit very very very slowly.
> 
> When I did a thread dump, almost all of the dispatcher threads were "waiting" 
> (i.e., parked not doing anything).

The interesting question (without which everything else is pure speculation) 
is: what were the active threads doing?

Regards,

Roland

> 
> The mailbox size grows into the millions during the test.  The main actor 
> never really catches up, just putt putts along, it doesn't get faster.
> 
> A few other notes:
> 1. I did not max out memory or hit stop the world GC at any point during the 
> test.
> 2. The CPU is very low on the machine, under 50%
> 3. There are no hardcore errors on the main actor, he doesn't restart or 
> anything like that
> 4. I am using Akka 2.2.3
> 
> So, my questions are:
> 1. If the threads aren't busy (they are waiting), why isn't my main actor 
> making faster progress?  Why are the other threads waiting seemingly not 
> doing anything?
> 
> 2. What might cause the system to seemingly "shut down"?
> 
> 
> -- 
> >> 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.



Dr. Roland Kuhn
Akka Tech Lead
Typesafe – Reactive apps on the JVM.
twitter: @rolandkuhn


-- 
>>  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.

[akka-user] Re: Storm-like framework implemented on Akka

2014-08-23 Thread Rafał Sobota

Have anything changed in this matter?

On Saturday, October 29, 2011 12:44:45 AM UTC+2, Evan Chan wrote:
>
> Yeah, I wrote this DSL. 
>
> However, I _really_ wish there was a Storm-like system implemented on 
> top of Akka.   I believe Storm's resilience and fault-tolerance is 
> built on top of monitoring processes.   Akka might offer not only 
> better fault tolerance, but much more flexible topologies.  Right now, 
> Storm topologies are fixed (ie cannot provision more workers/threads 
> without resubmitting the topology). 
>
> I think to match Storm, the Akka-based system would need the 
> following: 
> - at-least-once guaranteed message processing.   This is essentially a 
> system to track what parts of a tree of nodes has failed. 
> - distributed routing of messages, like is coming in Akka 2.x 
>   (by this I mean that N nodes can forward / route messages to N other 
> nodes, consistently, ie if my message hashes to actor 10, then no 
> matter which source actor this message is forwarded from, they all go 
> to actor 10.) 
> - distributed supervision and restarts 
> - a web UI for monitoring 
>
> -Evan 
>
>
> On Oct 28, 5:45 am, Debasish Ghosh  wrote: 
> > FWIW there is a Scala DSL for Storm ..
> https://github.com/velvia/ScalaStorm 
> >  .. 
> > 
> > cheers. 
> > 
> > On Fri, Oct 28, 2011 at 11:55 AM, Jesse Eichar 
> > wrote: 
>
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > > So Storm (https://github.com/nathanmarz/storm) has several 
> > > characteristics that I need for a project I am about to work on.  One 
> > > of my colleges has evaluated this project and while looking at it I 
> > > thought that Akka would be a perfect library for implementing Storm. 
> > > So I decided to ask the Akka community if they knew of an alternative 
> > > to Storm developed in Scala. 
> > 
> > > Basic requirements: 
> > > * Framework manages ensuring messages are delivered 
> > > * manages load balancing 
> > > * runs on multiple instances 
> > > * detects network/instance failures and compensates 
> > > * allows developer to only write application code and non of the above 
> > > considerations 
> > 
> > > Any thoughts? 
> > 
> > > Jesse 
> > 
> > > -- 
> > > You received this message because you are subscribed to the Google 
> Groups 
> > > "Akka User List" group. 
> > > To post to this group, send email to akka...@googlegroups.com 
> . 
> > > To unsubscribe from this group, send email to 
> > > akka-user+...@googlegroups.com . 
> > > For more options, visit this group at 
> > >http://groups.google.com/group/akka-user?hl=en. 
> > 
> > -- 
> > Debasish Ghoshhttp://manning.com/ghosh 
> > 
> > Twttr: @debasishg 
> > Blog:http://debasishg.blogspot.com 
> > Code:http://github.com/debasishg

-- 
>>  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.

[akka-user] Akka IO TCP sequential vs. stream-like decoding of incoming Bytestrings

2014-08-23 Thread Sebastian Georgi

Hey List!

My name is Sebastian and I'm fairly new to Scala and Akka :-) I've been 
working with Ruby (and Rails) amost exclusively for the last 7 years, but I 
decided it's time for some new input on functional patterns and strong 
types.

I want to create a simple Protocol that can be used for client-server 
event/count-logging. I already figured out how to prepend a fixed lenght to 
the Bytestring, as well as an identifier-Byte to define the incoming 
message's type, so the decoding and mapping of individual Bytestrings into 
Actor messages works quite well. I'm also planning to use my own client, 
which will probably just fire sequential Tcp.Write commands to the 
established connection. The handling Actor on the server's connection will 
basically decode the Bytestring, generate a Message and dispatch to another 
Actor.

I assume that I can send multiple Events in a single Bytestring, as they 
will be decoded recursively, and the server handling actor would just block 
until the Bytestring has as least be received (if I chose to pass decoding 
to another Actor). That'd be ok for me, since my logic tells me that the 
client just can't send another message until it has finished sending one.

So, how does streaming come in here? I've had a hard time understanding the 
now obsolete Pipelining construct of Akka 2.2, and I can surely see how 
that would streamline decoding, encoding (and even transport with 
TcpReadWriteAdapter). 

My question is: Do I even have to care about "streaming" for the above 
use-case of 1-on-1 client-server tcp connection? What benefits would emerge 
if I'd try to use Akka Streams? How would a hypothetical client do anything 
different than sending messages when it has been given the instruction to 
do so?

I've hit quite a wall researching on that topic in my spare time (that's 
where I learn Scala/Akka), so maybe someone could give me a hint on 
Stream-theory, an exemplary pattern for my use-case to have a good look at, 
a link for clarification or even a chapter of a book I'd buy? I'd also be 
happy to be told that I've been partly or fully wrong :-)

Thanks in advance and cheers,
-Sebastian

-- 
>>  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.

Re: [akka-user] Re: Storm-like framework implemented on Akka

2014-08-23 Thread Konrad 'ktoso' Malawski

Have anything changed in this matter?

https://spark.apache.org/

Happy hakking!

-- 
Konrad 'ktoso' Malawski
hAkker @ typesafe
http://akka.io

-- 
>>  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.

Re: [akka-user] Actor system unexpected slow down at load?

2014-08-23 Thread √iktor Ҡlang

Sounds like a possible visibility issue from the description.
On Aug 23, 2014 2:09 PM, "Roland Kuhn"  wrote:

>
> 23 aug 2014 kl. 02:37 skrev Paul Cleary :
>
> I have an actor system that is setup using all of the akka defaults.
>
> Nothing in the system has a lot of latency, we are talking about sub
> millisecond (20 microsecond) latencies.
>
> All traffic flows through a single actor to downstream actors.  This
> "main" actor just forwards the message onto children using a lookup.
>
> I am doing load testing, and have seen the same trend both on my local, as
> well as in a server environment.  The "main" actor keeps up superbly up
> until a certain point.
>
> I get up to about 1500 requests per second in my load test, which
> generates a boat load (10s of thousands) of messages against my single
> actor.
>
> At that point, all of a sudden the mailbox size gets enormous on my main
> actor.
>
> None of the downstream actors are doing anything, so it isn't like some
> roque actor is chewing up threads.
>
> The main actor IS making progress, albeit very very very slowly.
>
> When I did a thread dump, almost all of the dispatcher threads were
> "waiting" (i.e., parked not doing anything).
>
>
> The interesting question (without which everything else is pure
> speculation) is: what were the active threads doing?
>
> Regards,
>
> Roland
>
>
> The mailbox size grows into the millions during the test.  The main actor
> never really catches up, just putt putts along, it doesn't get faster.
>
> A few other notes:
> 1. I did not max out memory or hit stop the world GC at any point during
> the test.
> 2. The CPU is very low on the machine, under 50%
> 3. There are no hardcore errors on the main actor, he doesn't restart or
> anything like that
> 4. I am using Akka 2.2.3
>
> So, my questions are:
> 1. If the threads aren't busy (they are waiting), why isn't my main actor
> making faster progress?  Why are the other threads waiting seemingly not
> doing anything?
>
> 2. What might cause the system to seemingly "shut down"?
>
>
> --
> >> 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.
>
>
>
>
> *Dr. Roland Kuhn*
> *Akka Tech Lead*
> Typesafe  – Reactive apps on the JVM.
> twitter: @rolandkuhn
> 
>
>  --
> >> 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.
>

-- 
>>  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.

Re: [akka-user] Actor system unexpected slow down at load?

2014-08-23 Thread Paul Cleary

Thanks Ronald and Heiko.  Turns out, the code that was doing the monitoring 
\was the culprit.

I removed my monitoring, and everything took off from there.  I am 
considering this issue closed, I appreciate your help.


On Saturday, August 23, 2014 8:09:25 AM UTC-4, rkuhn wrote:
>
>
> 23 aug 2014 kl. 02:37 skrev Paul Cleary >:
>
> I have an actor system that is setup using all of the akka defaults.
>
> Nothing in the system has a lot of latency, we are talking about sub 
> millisecond (20 microsecond) latencies.
>
> All traffic flows through a single actor to downstream actors.  This 
> "main" actor just forwards the message onto children using a lookup.
>
> I am doing load testing, and have seen the same trend both on my local, as 
> well as in a server environment.  The "main" actor keeps up superbly up 
> until a certain point.
>
> I get up to about 1500 requests per second in my load test, which 
> generates a boat load (10s of thousands) of messages against my single 
> actor.
>
> At that point, all of a sudden the mailbox size gets enormous on my main 
> actor.
>
> None of the downstream actors are doing anything, so it isn't like some 
> roque actor is chewing up threads.
>
> The main actor IS making progress, albeit very very very slowly.
>
> When I did a thread dump, almost all of the dispatcher threads were 
> "waiting" (i.e., parked not doing anything).
>
>
> The interesting question (without which everything else is pure 
> speculation) is: what were the active threads doing?
>
> Regards,
>
> Roland
>
>
> The mailbox size grows into the millions during the test.  The main actor 
> never really catches up, just putt putts along, it doesn't get faster.
>
> A few other notes:
> 1. I did not max out memory or hit stop the world GC at any point during 
> the test.
> 2. The CPU is very low on the machine, under 50%
> 3. There are no hardcore errors on the main actor, he doesn't restart or 
> anything like that
> 4. I am using Akka 2.2.3
>
> So, my questions are:
> 1. If the threads aren't busy (they are waiting), why isn't my main actor 
> making faster progress?  Why are the other threads waiting seemingly not 
> doing anything?
>
> 2. What might cause the system to seemingly "shut down"?
>
>
> -- 
> >> 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.
>
>
>
>
> *Dr. Roland Kuhn*
> *Akka Tech Lead*
> Typesafe  – Reactive apps on the JVM.
> twitter: @rolandkuhn
> 
>  
>

-- 
>>  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.

[akka-user] Actor constructor lazy initialization?

2014-08-23 Thread Yogesh Shetty

I have recently ported some of my code to leverage akka framework and I 
randomly come across errors where I think actor constructor is not 
initialized completed. 

I have this ActorFactory class which spins of supervisor actor, and in each 
supervisor actor constructor i have code to spawn child actor as described 
below. 

class ActorFactory(factorybuilder:IFactoryBuilder) extends IActorFactory{

createActor[ConfigSupervisor](Props(new ConfigSupervisor(this)))
createActor[RabbitSupervisor](Props(new 
RabbitSupervisor(this,ConfigReader.getRabbitConfig)))
createActor[DAOChiefSupervisor](Props(new 
DAOChiefSupervisor(this,factorybuilder.daoFactory))) 

}


class DAOChiefSupervisor(factory:IActorFactory,daofactory:IDAOFactory) 
extends BaseSupervisor
{
  val log = LoggerFactory.getLogger(this.getClass())
 
  //Code to spin off child actor 
  val dao = factory.createChild[DAOSupervisor](this, Props(new 
DAOSupervisor(factory,daofactory)))
}

trait IActorFactory {

  val system = ActorSystem()
  var actorMaps= TrieMap[String,IActorURI]()
  val log = LoggerFactory.getLogger(this.getClass())
  
  def createActor[A:TypeTag](instance:Props)  : IActorURI = 
  {
  val name = getName[A]
  
  val newactor = ActorURI(system.actorOf(instance,name))
  actorMaps += (name -> newactor)
  log.info("Creating Actor " +name)
  newactor
  }

  def createChild[A:TypeTag](parent:Actor, instance:Props) :IActorURI = 
  {
val name = getName[A]
val newactor = ActorURI(parent.context.actorOf(instance,name))
actorMaps += (name -> newactor)
log.info("Creating Child Actor " +name)
newactor
  }
  def getActor[A:TypeTag]() = 
  {
val name = getName[A]
val actor = actorMaps.get(name)
actor match 
{
  case None => log.error(f"Actor $name not found")
  case _ =>
}
actor
  }


So what I am seeing is when I try to access DAOSupervisor from different 
lines of code it gives me error message saying Actor not found, so it looks 
like Actor constructor is not fully initialized when i get reference back. 

Thanks in advance for your help. 

-- 
>>  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.

Re: [akka-user] akka-persistence AtLeastOnceDelivery deliveryId generation

2014-08-23 Thread Arnout Engelen

Hi Patrik,

Thanks for your reply!

On Thursday, August 14, 2014 1:48:08 PM UTC+2, Patrik Nordwall wrote:
>
> On Thu, Aug 14, 2014 at 12:23 AM, Arnout Engelen  > wrote:
>
>> I'm using akka-persistence for a project and so far it's been a fairly 
>> pleasant experience.
>>
>> One thing I noticed was that when using AtLeastOnceDelivery, I must use 
>> the deliveryId's generated by the trait. In some cases it could be nice 
>> if I could provide my own semantically meaningful keys as deliveryId 
>> instead.
>>
>
> We considered it when we designed AtLeastOnceDelivery, but came to the 
> conclusion that it was easiest to understand and most safe to provide the 
> correlation id. That does not mean that sending that id to the recipient is 
> the only way to do it. You could create a mapping between this id and some 
> other id that is passed to the recipient.
>  
>
>> (of course I could try and work around this by keeping track of a mapping 
>> between deliveryId's and my own meaningful id's, but that doesn't seem 
>> right at all :) ).
>>
>
> exactly, why would that not be right? 
>

I'm not sure - it tempted me to write 
https://gist.github.com/raboof/f5d3a500bdfc758dfb9b , which feels like it 
duplicates some of what AtLeastOnceDelivery is already doing (and makes a 
*bit* of a potential mess of retransmissions/UnconfirmedWarning's, though 
it's managable).

Does this seem OK to you, or would you approach it some other way?


Kind regards,

Arnout

-- 
>>  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.

Re: [akka-user] Actor system unexpected slow down at load?

Re: [akka-user] Actor system unexpected slow down at load?

[akka-user] Re: Storm-like framework implemented on Akka

[akka-user] Akka IO TCP sequential vs. stream-like decoding of incoming Bytestrings

Re: [akka-user] Re: Storm-like framework implemented on Akka

Re: [akka-user] Actor system unexpected slow down at load?

Re: [akka-user] Actor system unexpected slow down at load?

[akka-user] Actor constructor lazy initialization?

Re: [akka-user] akka-persistence AtLeastOnceDelivery deliveryId generation

9 matches

Site Navigation

Mail list logo

Footer information