Are you using ReactiveMongo? If so what version? Have you investigated bulkInsert, perhaps buffer locally and only flushing when a certain limit is reached?
What do your write queues in MMS look like? Can you clarify what actors you believe are not terminating properly? On Friday, April 10, 2015 at 1:07:01 PM UTC-4, Dan Martin wrote: > > I have a feeling that what's happing is my actors are not terminating > gracefully. See, my benchmark app runs for a finite time. Once that time > is reach, it shuts down the actor system. I believe there are messages in > the actor mailboxes that don't get processed. I'm just now reading through > some documentation about graceful shutdowns. > > http://letitcrash.com/post/30165507578/shutdown-patterns-in-akka-2 > > > On Friday, April 10, 2015 at 12:25:15 PM UTC-4, Dan Martin wrote: >> >> I'm building an app-monitoring application in Play 2 and MongoDB 3. >> Basic usage is client application log messeges via REST endpoints provide >> by my Play app. For benchmark testing, I put together a client tool where >> I use Akka to simulate application requests. I'm using the Akka Scheduler >> to send messages to a logBotActor (LogBot is the name of my benchmark >> tool). The logBotActor pics from a random set of messages that I have >> predefined in a list and sends them to sendMessageActor for sending the >> HTTP request to my app monitory application >> The scheduler is configured to run at a 1ms interval. So, in theory, I >> should see 1000 messages logged on the backend (MongoDb) for each second >> that goes by, but Im not. In fact, I'm no where near that figure. I >> understand that there's latency involved (my app-monitor is running on >> Heroku). I also understand that from the time the scheduler kicks off a >> message, CPU clock cycles go by as messages are passed around between the >> actors and performing the random calculation for getting random predefined >> messages. But eventually, it should all catch up, right?? >> >> I'm just getting my feet wet with Akka, so I'm sure there's some tuning >> that needs to be addressed. >> >> >> Here is my application.conf. (note: I omitted the debugging related >> properties). I've tried adjusting the parallelism-max and throughput but >> they didn't seem to effect anything. >> >> akka { >> actor { >> >> default-dispatcher { >> executor = "fork-join-executor" >> fork-join-executor { >> parallelism-factor = 2.0 >> parallelism-max = 10 >> parallelism-min = 2 >> } >> throughput = 100 >> } >> } >> } >> >> >> >> Here are my machine's specs: >> >> *MacBook Pro (15-inch, 2.53GHz, Mid 2009)* >> *Processor* 2.53 GHz Intel Core 2 Duo >> *Memory* 8 GB 1067 MHz DDR3 >> >> >> -- >>>>>>>>>> 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.
