whould it plausible to inline the function and how to get the on the Oldbecome ?
How could it be done for multiple requests?
How i am currently doing things with requestIds, it is getting very fragmented and i think that i would get problems in 12monath to read and navigate in my own code
@Ralf1108 There's work in progress to support named pipes in v1.5
ok cool :-)
would be cool to support scenarios for multi process akka systems without opening a port and hassle with firewall rules
Can somebody shine a light on what happened to AsyncBehavior.Suspend/AyncBehavior.Reentrant on Receive? I need to do bunch of operations, but i dont want to waste thread on blocking, and Suspend is the thing that im looking for
@sonicflare Are you looking for ReceiveAsync<T>(Func<T, Task>)?
AsyncBehavior got dropped a long time ago, only Suspend is supported now, there is an overload of Receive that accepts a Func<T, Task> it have been renamed to ReceiveAsync in 1.0.7
@JeffCyr looks like it, and it does the suspend by default? So while it is waiting for stuff to complete, no other messages for this actor is processes, right?
Hi, Any sample on how to send Actor (Initiating actor in choreography) inside a meesage in Cluster environment? Thanks
For a monitoring solution for our services (not using clustering), what would be the best way to present a "list/tree" of actors of a local actorsystem. Having each actor respond to a "getchildren" message or is there a way to ask the actorsystem this? Is there a way to traverse the actor tree?
@christiansparre the get list/tree its the same as to work with system file directories. You need to ask each folder for the child-items. But i dont know if there is a system message for doing it like Akka.Actor.Identity
There is no officially supported way of doing this. But there is a hacky one.
Hi, AroundReceive for UntypedActor allways returns true and ReceiveActor inherites from UntypedActor without changing this behavior. Shouldn't ReceiveActor return false for AroundReceive if for some reason the message wasn't handled by a Receive function defined in a ReceiveActor?
@Horusiath sorry for the minimalism. I have a custom serializer (ProtoBuf.Net) for type Message. Message has (among others) IActorRef property for the initiator actor. In the samples you mentioned the default serializer is used as far as i can tell. Might be ISurrogated interface which should be surrogated? I guess the question is more is passing IActorRef around good practice? In a low-latency application what is the overhead of the resolving for each message?
@JeffCyr If I want to log handled messages (commands) to a message store in my ReceiveActor without doing it in every receive function, how would I do that? I thought I could use AroundReceive for this, guess not. Feels a bit inconsistent but I think i'm missing something.
@Lejdholt Do you expect an actor to receive a lot of unhandled messages? Why not log every messages?
@JeffCyr No but I dont want to store commands that wasn't handled. Storing commands are for followup, what command resultet in that event, through correlationids and causationids
Is there a more advanced way to control ITellScheduler? Cron-like for instance. Currently ITellScheduler provides initial delay and iterval. I want something like once at 2AM during workdays, stuff like that. Thanks
logging commands to a "normal" log is already done in the parent actor.
@eyantiful in order to serialize IActorRefs, serializer must support surrogates (both Wire and JSON.NET do), otherwise you'd need to pass it i.e. string determining path to an actor, and then resolve it by yourself.
passing IActorRef is good, if used when necessary. Also how low-latency do you mean?
@Horusiath we should support 15k concurrent msgs in under 100ms. When you say resolving do you mean ActorSelection?
@eyantiful Are you able to batch messages? Akka.Remote cannot handle 150K msg/sec
We are working on increasing the performance of Akka.Remote in v1.5
@JeffCyr are you talking from single node? the figures are for the cluster as a whole.
@JeffCyr Im currently POC to see how far can we go with minimum nodes in order to asses cluster size...
@eyantiful Yes I meant for a single node, I made a benchmark with two nodes on the same machine on loopback, I could get ~6K msg/sec
On v1.5 we were at 100K msg/sec for the same test, and there were still room for improvements