Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 14:21
    Ralf1108 edited #3933
  • 14:17
    Ralf1108 opened #3933
  • 12:57
    Aaronontheweb commented #3904
  • 12:15
    Aaronontheweb synchronize #3927
  • 11:21
    Zetanova synchronize #3916
  • 08:35

    Aaronontheweb on dev

    Fix build script to be able to … (compare)

  • 08:35
    Aaronontheweb closed #3924
  • 08:28
    Aaronontheweb synchronize #3927
  • 08:28
    Aaronontheweb synchronize #3924
  • 08:28

    Aaronontheweb on dev

    added updated Windows Release p… Merge pull request #3869 from A… Fixed Akka.Remote.ResendUnfulfi… and 6 more (compare)

  • 08:28
    Aaronontheweb closed #3932
  • 08:22
    Aaronontheweb opened #3932
  • 08:16

    Aaronontheweb on 1.3.15

    (compare)

  • 08:14

    Aaronontheweb on master

    Fixed Akka.Remote.ResendUnfulfi… added v1.4.0-beta2 release note… added Akka.NET v1.3.15 release … and 2 more (compare)

  • 08:14
    Aaronontheweb closed #3931
  • 08:11
    Aaronontheweb synchronize #3931
  • 07:59
    Aaronontheweb commented #3905
  • 07:58
    Aaronontheweb edited #3931
  • 07:57
    Aaronontheweb commented #3889
  • 07:54
    Aaronontheweb synchronize #3931
Aaron Stannard
@Aaronontheweb
in this case the reason why you're seeing two instances of the exception
one is for the client currently connected to another node
the other is for the socket that is used to accept inbound connections
Peter Bergman
@peter-bannerflow
Nice, I wa actually scratching my head over that one as well
Aaron Stannard
@Aaronontheweb
yeah, it's annoying
the exception gets thrown on that Socket.Receive call
which is basically what's going to be run asynchronously by the SocketAsyncEventArgs object we're using
we could probably handle that up the stack better
so in effect
the fact that we have these inocuous errors
is a user-experience issue on our part
Aaron Stannard
@Aaronontheweb
makes the user think they did something wrong
when they didn't
Peter Bergman
@peter-bannerflow
Yeah
Aaron Stannard
@Aaronontheweb
We might release 1.1.1 today
depends on if I can get one more hostname / binding bug fixed
fixed IPV6 support already
have one more issue with public-hostname that needs to be resolved
Peter Bergman
@peter-bannerflow

Here goes a kind of an open question... Does anyone have some insights to share on Akka.Cluster perfomance in terms of throughput of messages from the network into the actor system. For example, what kind of throughput can we expect to one single actor (running on one machine) that receives messages from other remote nodes in the cluster? Of course it depends on what that actor actually do with the messages as well as hardware specs and such but any insights would be appreciated. Real world experience anyone? For example, can we expect 10k messages/second or 100k messages/second. I have seen this article https://petabridge.com/blog/performance-testing-mandatory/ and from that I gather that around 10k messages/second is reasonable?

Also, does anyone have some insight in OS (Windows Server) level tweaks that could be made in order to increase the message throughput into the actor system from the network?

Aaron Stannard
@Aaronontheweb
check out the benchmarks on each pull request
green check mark next to perf-tests
that will take you to a folder chock full of them
there's remote one way and remote two way specs for the current transport
two way is a full request response chain
Peter Bergman
@peter-bannerflow
Hmm yeah ok, I found a lot of them (like this for example http://petabridge-ci.cloudapp.net/viewLog.html?buildId=13097&buildTypeId=AkkaNet_AkkaNetWindowsPerformanceTests&tab=artifacts) if that is what you mean?
Aaron Stannard
@Aaronontheweb
yep
the Akka.Remote Helios transport ones
are the live transport
Peter Bergman
@peter-bannerflow
Yeah ok
Aaron Stannard
@Aaronontheweb
now I just gave a talk on this yesterday
that's a benchmark for our hardware, for our spec
there's no such thing as a global benchmark
Peter Bergman
@peter-bannerflow
Really... is it recorded? :)(
Aaron Stannard
@Aaronontheweb
yep
let me find it
Peter Bergman
@peter-bannerflow
Cool
my talk was only 30 minutes long
so I have no idea why the video is 60 minutes
Arjen Smits
@Danthar
lol that screenshot
Peter Bergman
@peter-bannerflow
Thx
Arjen Smits
@Danthar
its like: "kudos to that guy with the question!"
Peter Bergman
@peter-bannerflow
About the files, is two way (Akka.Remote.Tests.Performance.Transports.HeliosRemoteMessagingThroughputSpec+TwoWay) like an actor receiving a message from the network and then responding with a message to the sender?
Aaron Stannard
@Aaronontheweb
just an FYI: I got some of the causes and reasons behind the prior performance issues with Akka.Remote mixed up during the talk because I couldn't see my notes with the way our monitors were laid out
so I was going from memory, and some of that turned out to be mixed up
the lazy evaluation stuff was actually an issue with slowly creating / shutting down children
different performance issues
but aside from the technical detail there, the major point is true
Peter Bergman
@peter-bannerflow
Alright
Aaron Stannard
@Aaronontheweb
@peter-bannerflow yep, that's correctr