Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 21:29
    Aaronontheweb commented #3863
  • 21:28
    Aaronontheweb synchronize #3863
  • 21:18
    Aaronontheweb synchronize #4000
  • 21:17
    Aaronontheweb commented #3964
  • 21:17
    Aaronontheweb commented #3964
  • 21:16
    Aaronontheweb synchronize #3964
  • 21:12
    Aaronontheweb commented #3964
  • 21:08
    Aaronontheweb synchronize #71
  • 21:04
    Aaronontheweb synchronize #3973
  • 21:00
    Aaronontheweb commented #71
  • 20:58

    Aaronontheweb on dev

    Akka.Persistence.TCK fix - chec… (compare)

  • 20:58
    Aaronontheweb closed #4002
  • 20:51
    Aaronontheweb synchronize #4002
  • 20:45
    Aaronontheweb commented #3811
  • 20:45
    Aaronontheweb commented #3811
  • 20:44
    Aaronontheweb labeled #4002
  • 20:43
    Aaronontheweb milestoned #4002
  • 20:43
    Aaronontheweb opened #4002
  • 20:37
    Aaronontheweb synchronize #71
  • 20:20
    Aaronontheweb synchronize #71
Aaron Stannard
@Aaronontheweb
NBench has a couple of new things in that release I'm excited about
the ElapsedTimeAssertion is pretty cool for long-running stuff
the plugin model for instrumenting metrics from sources NBench doesn't support by default
Corneliu
@corneliutusnea
@Aaronontheweb You should have let the change of Process Priority even when run in concurrent mode
Aaron Stannard
@Aaronontheweb
oh, the thread priority?
no, the Process priority not the thread
Aaron Stannard
@Aaronontheweb
damn, so you're right
mind sending me a PR for that - now I have an excuse to fix the logo too
v0.2.1 :p
you can just pass the Concurrent flag into the SetProcessPriority flag and change it there
so we skip the affinity part but leave the priority
Corneliu
@corneliutusnea
done
argh ... just noticed ... tabs vs spaces in files .. my fault ... leave it like that for now, code is correct
Aaron Stannard
@Aaronontheweb
don't make me go all whitespace religion on you pal!
I'll fix that in the release - there's a tool in VS that keeps this stuff consistent project to project
can't remember what it is anymore
Corneliu
@corneliutusnea
I'm willing to start a fight :) pro Tabs :) hahahah
Aaron Stannard
@Aaronontheweb
spaces always win since the Tabalamo
Aaron Stannard
@Aaronontheweb
@corneliutusnea ok, got that out
made some minor changes to the file (SPACES FOREVER)
build server is cranking it out now
Corneliu
@corneliutusnea
awesome
Corneliu
@corneliutusnea
@Aaronontheweb I have lots of messages that have to go to specific actors (by path) but those actors might not be created
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