Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Oct 16 22:15
    Aaronontheweb synchronize #3889
  • Oct 16 21:00
    dependabot-preview[bot] synchronize #3986
  • Oct 16 21:00

    dependabot-preview[bot] on nuget

    Bump NUnit from 3.6.1 to 3.12.0… (compare)

  • Oct 16 21:00
    dependabot-preview[bot] synchronize #3985
  • Oct 16 21:00

    dependabot-preview[bot] on nuget

    Bump FsCheck.Xunit from 2.9.0 t… (compare)

  • Oct 16 21:00
    dependabot-preview[bot] synchronize #3983
  • Oct 16 21:00

    dependabot-preview[bot] on nuget

    Bump ApprovalUtilities from 3.0… (compare)

  • Oct 16 21:00
    dependabot-preview[bot] edited #3985
  • Oct 16 21:00
    dependabot-preview[bot] edited #3986
  • Oct 16 21:00
    dependabot-preview[bot] synchronize #3982
  • Oct 16 21:00
    dependabot-preview[bot] synchronize #3987
  • Oct 16 21:00

    dependabot-preview[bot] on nuget

    Bump FsPickler from 5.2.0 to 5.… (compare)

  • Oct 16 21:00

    dependabot-preview[bot] on nuget

    Bump LightningDB from 0.9.8 to … (compare)

  • Oct 16 21:00
    dependabot-preview[bot] edited #3982
  • Oct 16 21:00
    dependabot-preview[bot] edited #3983
  • Oct 16 21:00
    dependabot-preview[bot] edited #3987
  • Oct 16 20:59
    dependabot-preview[bot] edited #3982
  • Oct 16 20:59
    dependabot-preview[bot] edited #3985
  • Oct 16 20:59
    dependabot-preview[bot] edited #3987
  • Oct 16 20:59
    dependabot-preview[bot] edited #3986
Bart de Boer
@boekabart
isn't that just thread prio?
Aaron Stannard
@Aaronontheweb
nah
the foreground threads are meant to be literally used for user-facing elements
so like the UI thread in an app
Bart de Boer
@boekabart
let me quickly test that theory
Aaron Stannard
@Aaronontheweb
or the thread that owns the console UI
I don't have the details 100% clear off the top of my head anymore
but basically a process can't exit until its foreground threads are joined
Bart de Boer
@boekabart
Yeah, that fixed it.
still a normal console app (not topshelf) didn't suffer from it, it seems. But that one also did less work on that threadpool, so apples and oranges
Aaron Stannard
@Aaronontheweb
akkadotnet/akka.net#2028
just created that
foreground vs. background doesn't change priority
it's the exit behavior that gets affected
Bart de Boer
@boekabart
ok, clear! Re priority btw, again/still suffering from remote disconnects during load; what was that timeout setting again?
I think - there's other settings in there you can adjust also
Bart de Boer
@boekabart
thanks, let's try that..
Aaron Stannard
@Aaronontheweb
one thing we might be able to do, possibly
is add a configuration setting to the ForkJoinDispatcher and the dedicated thread pool
which will allow you to change the priority
I'm comfortable leaving the default where it is
but also fine with users being able to change it
Tomasz Jaskula
@tjaskula
quick question, does the code shared between the actors needs to be synchronized with lock or maybe there some other ways of doing things ?
Aaron Stannard
@Aaronontheweb
@tjaskula you mean shared memory?
every actor instance's memory should be made private
and not shared
if you do need to share data
you should pass that data in an immutable message
that way there's no need for locks and synchronization
and you can still have a high degree of parallelism
Tomasz Jaskula
@tjaskula
I meat rather using for example a common portion of code
like for example you write it once and then you use it for several actors
Aaron Stannard
@Aaronontheweb
oh
just methods / functions?
Tomasz Jaskula
@tjaskula
let say I have something I want to use on PreRestart for every actor
like writing to some DB log or something
Aaron Stannard
@Aaronontheweb
ah
every one of those actors
should be given their own instance of that object
part of the goal of the actor model
is to avoid locking / shared state concurrency
the other thing you can do
if you don't want every actor to have to hold onto a DB connection
is to create a single type of actor who's job it is to write stuff to the DB
and give everyone else a reference to an instance of that actor type
Tomasz Jaskula
@tjaskula
thanks @Aaronontheweb
Aaron Stannard
@Aaronontheweb
@JaspritBola hmm... after downing a node it should be removed
and no further attempts should be made to contact it
if it's not getting removed then that's a bug