yeah, at any given time we had 50 people concurrently, but it ended up being north of 100 total who had attended the meetup for at least some portion of time
so the akkaio stuff for tcp, would that share listening port across actors
or does it require port per
@cpx you ran the serializer in debug mode, right?
beating protobuf when no version tolerance :D
Hi, I'm looking a bit on Akka.Cluster and see a lot of examples with routing. Is all communication with actors when using Akka.Cluster done through routing? I might have some actors that there should only be one of. How do I get a hold of that one? I've been looking around the WebCrawler sample and I see a lot of routers...
Ivan R. Perez
@Aaronontheweb just a heads up, I put in a pull-request for a bug I found with the performance counters.
thanks @irperez - I appreciate that. I'm glad you caught it.
Despite that bug though, Akka.Monitoring working out well for you?
Ivan R. Perez
It is. The perf counters are great. Its the insight I needed.
@rogeralsing Now that you mention it, yeah I did. Those are awesome numbers!
finished our Akka.Cluster contributor's meeting - we did a pretty job documenting and exploring how the multi-node test runner actually works. If you folks are interested in working on Akka.Remote, Akka.Cluster, Cluster.Sharding, etc... this is good stuff to know: https://www.youtube.com/watch?v=xwmHWnIUmTY
@Aaronontheweb sounds great, will definitely check it out :+1:
I've seen it, great job :+1:
btw. since event adapter stuff is done, I want to standarize SQL-based journals a little (Akka.Persistence.Sql.Common) and add a querying capabilities to them (my proof of concept branch)
@Horusiath I saw your question about SQL.Common earlier
each of the Akka.Persistence implementations gets a nightly integration test anytime our dev branch changes
where we automatically upgrade them to the latest version of Akka.NET
this addresses problems with querying event journal for aggregated data across many persistent actors
including their other dependencies
great :) this should help, when I'll start to mess around
supports AppInsights, StatsD, and now performance counters
as for measuring the queue length of the mailbox - unfortunately there isn't a public API to access that :\
we'll be working on that when we do a more "holistic" solution for integrating monitoring directly into Akka.NET core
essentially we're going to have an engine in place, not too different from our logging engine, which will expose metrics and drains for collecting those sorts of metrics
that's a way's out for the time being though - no plans to start on that until some other big pieces of infrastructure (i.e. Akka.Cluster, TLS) are finished
Hey all, For long lived/single instance dependencies (in my case neo4jclient) what is the appropriate pattern for passing that dependency to an actor? Pass the instance to the constructor or factory method for use in PreRestart? Should PostRestart be overridden as not to call PreRestart again? I'm sure i found some succinct doco/examples somewhere, but for the life of me I can't find it. Many thanks!
@Aaronontheweb thanks for that info
What's the best mechanism to limit requests on an external API without hitting their request limits (per account*)? I have multiple API credentials each with their own limit.
@rogeralsing I know that you're working on Wire for fun / proof of concept - but I think, it's a good moment to talk with Typesafe guys about common way of message serialization between JVM/.NET specifically for the akka needs. I know that they have hard time using default Java serializer too.
Ok, I'll ping them :)
Been testing Akka.Cluster and have tried out not using seed nodes, but instead joining the cluster. It seems that a joined node will be connected to other nodes, but will it give me problems down the line?
@rogeralsing You may have a small PR for Wire now ;)