Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 03:08
    hhko commented #4094
  • Dec 13 21:37
    Aaronontheweb commented #4085
  • Dec 13 20:28
    IgorFedchenko commented #4085
  • Dec 13 20:27
    IgorFedchenko commented #4085
  • Dec 13 15:38
    Aaronontheweb labeled #4096
  • Dec 13 15:38
    Aaronontheweb milestoned #4096
  • Dec 13 15:38
    Aaronontheweb labeled #4096
  • Dec 13 15:38
    Aaronontheweb opened #4096
  • Dec 13 10:41
    peirens-bart opened #4095
  • Dec 13 08:37
    Aaronontheweb synchronize #4071
  • Dec 13 08:13
    jiyeongj opened #4094
  • Dec 12 15:42
    Aaronontheweb synchronize #4086
  • Dec 12 15:42
    Aaronontheweb closed #4083
  • Dec 12 15:42

    Aaronontheweb on dev

    Fix #4083 - Endpoint receive bu… (compare)

  • Dec 12 15:42
    Aaronontheweb closed #4089
  • Dec 12 15:42
    Aaronontheweb labeled #4093
  • Dec 12 15:42
    Aaronontheweb labeled #4093
  • Dec 12 15:42
    Aaronontheweb labeled #4093
  • Dec 12 15:42
    Aaronontheweb opened #4093
  • Dec 12 14:20
    Aaronontheweb commented #4092
Corneliu
@corneliutusnea
as the init part of the actor is quite expensive so I want to create them on demand only
Aaron Stannard
@Aaronontheweb
create some parent actors who just listen for incoming messages
Corneliu
@corneliutusnea
is is a good pattern to send the message to a "parent" that checks if the child is created, if not create it then forward the message? This is going down 4-7 layers.
Aaron Stannard
@Aaronontheweb
oh yeah
was about to suggest that
first pattern we teach in our design patterns course does that
"child per entity" pattern
Corneliu
@corneliutusnea
the issue I see is that instead of one message going from A => G I end up with 10 intermediate messages
Aaron Stannard
@Aaronontheweb
yeah, but that's extremely fast in-memory
Corneliu
@corneliutusnea
well, once you add the overhead in each layer to check if children are there .. it starts to add up
Aaron Stannard
@Aaronontheweb
the overhead of checking on the first layer of node is going to be the same as routing all the way down to the bottom node
that's how actor selections work
Corneliu
@corneliutusnea
yeah, I have 4-7 layers, each with their own checks
Aaron Stannard
@Aaronontheweb
those checks on whether a child exists or not are very fast
it's a constant time read operation
since it uses a hash
(dictionary)
Corneliu
@corneliutusnea
would it be more efficient to listen to the dead-message queue (somehow?) and notice the target children was not there, init all the actors from A .. G and repost the message?
Aaron Stannard
@Aaronontheweb
you'd have to test it
the dead letters system might end up becoming a bottleneck if you're dealing with message volumes at the level where this is a concern
Corneliu
@corneliutusnea
it would be a bit more reactive, I generally have bursts of messages so if one inits the A..G then the rest of messges will be happy
bugger
Aaron Stannard
@Aaronontheweb
the overhead of checking to see if a child exists is very loiw
Corneliu
@corneliutusnea
your overhead yes, but I have my own checks
Aaron Stannard
@Aaronontheweb
doing that N times won't be too bad - what you should eventually do though is have that leaf node child reply to the sender
and then have the sender and leaf communicate directly after that if there needs to be a "conversation"
that way you only pay for the checks once
since each will hold an actor ref to each other
Corneliu
@corneliutusnea
hm, but then if it dyes ?
Aaron Stannard
@Aaronontheweb
Context.Watch
get a deathwatch notification
and then go back through the hierarchy again
Corneliu
@corneliutusnea
ok .. so there is no way for a parent to monitor the dead-messages for their potential children
Aaron Stannard
@Aaronontheweb
there is, but all dead messages go globally to the same place
Corneliu
@corneliutusnea
yeah, so that was my question, I want to pick/intercept that in the parent not globally
Aaron Stannard
@Aaronontheweb
yeah, not possible to do that
parent can check if the child exists first
before routing the message to it
and that's the preferred way of dealing with it
Corneliu
@corneliutusnea
guys, is there a way to "consolidate" somehow multiple logs based on some correlation id?
"old school" code we used to be able to track multiple logs by the thread-id most of the times, now I get logs from all over the place
Alex Valuyskiy
@alexvaluyskiy

@Aaronontheweb Have you plan to update Persistence providers for 1.0.7? I've already made pull requests for PostgreSql and SqlServer (Akka 2.4.2 compatible) providers
akkadotnet/Akka.Persistence.PostgreSql#20
akkadotnet/Akka.Persistence.SqlServer#24

and created MySql provider
https://github.com/alexvaluyskiy/Akka.Persistence.MySql
Is it possible to move this mysql implementation to akkadotnet github account?

Corneliu
@corneliutusnea
no idea what correlates with wht
Alex Valuyskiy
@alexvaluyskiy
@Aaronontheweb also it would be good to release a new version of Wire serializer, because 0.0.6 version has a lot of bugs
Vagif Abilov
@object
Hello, I just posted a question on SO where I express my unhapinnes about message boxing in F# actors. Here it is:
http://stackoverflow.com/questions/36470453/how-should-f-actor-functions-be-defined-to-avoid-message-boxing
I must say while I enjoy Akka.NET F# API and prefer it to C#, this particular aspect looks better in C#.
Bartosz Sypytkowski
@Horusiath
@object why are you boxing them at all?
and are you using Akka.FSharp?
Vagif Abilov
@object
Yes I am using Akka.FSharp. I am boxing to be able to match messages of different types.
Bartosz Sypytkowski
@Horusiath
from my perspective this is usually a problem with handling system messages