Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 13:04
    atrauzzi edited #4229
  • 12:57
    atrauzzi commented #4229
  • 12:07
    imkow commented #4017
  • 06:43
    dependabot-preview[bot] labeled #4230
  • 06:43

    dependabot-preview[bot] on nuget

    Bump FsPickler from 5.3.1 to 5.… (compare)

  • 06:43
    dependabot-preview[bot] opened #4230
  • 05:38
    Aaronontheweb commented #4229
  • 05:38
    Aaronontheweb commented #4229
  • 03:29
    atrauzzi opened #4229
  • Feb 17 21:57
    Arkatufus edited #4228
  • Feb 17 21:46
    Arkatufus synchronize #4228
  • Feb 17 20:17
    Arkatufus synchronize #4228
  • Feb 17 19:55
    Arkatufus opened #4228
  • Feb 17 19:14
    Arkatufus synchronize #4226
  • Feb 17 18:28
    Aaronontheweb commented #4226
  • Feb 17 18:27
    Aaronontheweb commented #4226
  • Feb 17 18:23
    Aaronontheweb synchronize #4226
  • Feb 17 18:23

    Aaronontheweb on nuget

    (compare)

  • Feb 17 18:23

    Aaronontheweb on dev

    Bump Google.Protobuf from 3.11.… (compare)

  • Feb 17 18:23
    Aaronontheweb closed #4225
Aaron Stannard
@Aaronontheweb
what I'd like to do ideally is add a benchmarking system for Akka.Cluster
test how different cluster sizes perform
and make it pluggable for people's apps
as for what you were saying @coffeeyesplease - I think the reason the recieving end is slower is because of how remote messages get delivered to their recipients
coffeeyesplease
@coffeeyesplease
[disclaimer]: I’m not experienced with neither helios os Akka.Net
Aaron Stannard
@Aaronontheweb
I think everything gets done as an actor selection
coffeeyesplease
@coffeeyesplease
I’ve with helios and it was damn fast
Aaron Stannard
@Aaronontheweb
so it takes some time to resolve each of those to an ActorRef
coffeeyesplease
@coffeeyesplease
I can’t remember teh numbers but it was really fast, but for some strange reason I was losing some of the messages
Aaron Stannard
@Aaronontheweb
if it was the same message each time and it didn't get logged by dead letters then it could be an issue with Helios' message decoding
Roger Johansson
@rogeralsing
Actually, i did see some messageloss when i had the students writing their paper
coffeeyesplease
@coffeeyesplease
hmmm!!!
Aaron Stannard
@Aaronontheweb
next thing I'm working on after we ship Akka.Cluster is Helios 2.0, which has a better model for dealing with that problem
it's going to follow Netty's design much more closely than the current version
(Akka.Cluster will ship after Akka.NET 1.0 is released)
Roger Johansson
@rogeralsing
Aaron, we should take a look if that was just my naive testcase or if it is a real issue
Aaron Stannard
@Aaronontheweb
if you have some bits that you can send me i can take a look
if it's a Helios issue then I know exactly where the problem is
it's the LengthFrameDecoder
either it or the ByteBuf sitting on top of it grabs only a partial chunk of a message
coffeeyesplease
@coffeeyesplease
yeah, I try and find the test
Aaron Stannard
@Aaronontheweb
the decoder reads some bytes that aren't actually the length-frame header
assumes the message is corrupt
and discards bytes until the buffer is empty
coffeeyesplease
@coffeeyesplease
it as basically sending logs messages the around. 128 len string
Aaron Stannard
@Aaronontheweb
it's possible that there's some race conditions I never caught with the reactive part of the socket
Roger Johansson
@rogeralsing
Found their test, mailed you
Aaron Stannard
@Aaronontheweb
thanks
I'll take a look at that
I've had a spec written down on paper, quite literally - in my notebook, for Helios 2.0 and I'm desperate to work on it because I think it'll finally be easy to work directly with Helios once I've made those changes :p
Helios' current API is simple but not the most intuitive
Aaron Stannard
@Aaronontheweb
@rogeralsing btw, have virtual nodes and all of that fun stuff implemented now
had to rewrite our Murmur3 implementation in order to support it
(followed the Scala implementation - it wasn't so different from mine, just optimized for being able to construct a hash in discrete steps)
(rather than treating it like a black-box all-or-nothing operation)
Roger Johansson
@rogeralsing
Nice :)
Roger Johansson
@rogeralsing
@Horusiath are you by any chance an old WoW gamer? from the looks of your alias :)
Aaron Stannard
@Aaronontheweb
@/all Unit2 for Akka.NET bootcamp is now available ;) https://github.com/petabridge/akka-bootcamp/tree/master/src/Unit-2
jcwrequests
@jcwrequests
@aaronontheweb the boot camp looks awesome. I will be adding it to my personal work load for the coming week. Good job 👍
Aaron Stannard
@Aaronontheweb
thanks @jcwrequests! We still have unit 3 to come yet but that'll be a ways off - unit 2 covered a lot of stuff, especially for folks who want to do WinForms / WPF / client programming with Akka.NET
jcwrequests
@jcwrequests
@Aaronontheweb Thanks again for sending the information on Resizer with Routing. The only problem is I can not figure out how to hook up the resizer to a ConsistentHashingGroup. The example you provided with with round robins. Any advice?
Aaron Stannard
@Aaronontheweb
Resizers only work with ConsistentHashingPool :p
group routers don't manage their routees
however, for turning on a resizer with consistent hashing pools
let me see if I can find a config example for that - about to head out but I'm in the middle of updating all of the consistent hashing routers now
brought them up to code with JVM akka, includes fun stuff like virtual nodes
jcwrequests
@jcwrequests
Okay got it. I will check that out. It should be fun once I get it hooked up to my eventstore with aggregates.
Once I get that done I may see if I have any Azure time left at work and try a stress test. My small Asus Ultra slim with an i5 is not the best for that sort of thing. Thanks again. I am will talk to you soon. Signing off here on the east coast.
One last thing I am blogging all about this experience so I may ping you with some research questions. Cheers and have a good one.
Håkan Canberger
@HCanber
I'm seeing PR:s (like #689 and #691) with no explanation to why they are submitted. I think A PR should at least have a sentence or two explaining why the changes are being made and what the changes are, even if it's only white space changes. In the case of #689 several bugs were introduced. An explanation to why the changes were made could have saved me some time, instead I had to decipher what was done, and trying to figure out why it had been changed. Thoughts?