Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Feb 21 19:37
    Arkatufus synchronize #4228
  • Feb 21 19:37
    Arkatufus ready_for_review #4228
  • Feb 21 15:42
    Aaronontheweb assigned #4241
  • Feb 21 15:42
    Aaronontheweb milestoned #4241
  • Feb 21 15:42
    Aaronontheweb labeled #4241
  • Feb 21 15:42
    Aaronontheweb labeled #4241
  • Feb 21 15:42
    Aaronontheweb labeled #4241
  • Feb 21 15:42
    Aaronontheweb opened #4241
  • Feb 21 01:47
    Arkatufus opened #4240
  • Feb 21 00:10
    Aaronontheweb synchronize #4212
  • Feb 20 23:50
    Aaronontheweb synchronize #4238
  • Feb 20 23:48
    Aaronontheweb commented #4234
  • Feb 20 23:47
    Aaronontheweb synchronize #4212
  • Feb 20 23:46

    Aaronontheweb on dev

    close #4234 - added CachingConf… (compare)

  • Feb 20 23:46
    Aaronontheweb closed #4239
  • Feb 20 23:46
    Aaronontheweb closed #4234
  • Feb 20 23:25
    Aaronontheweb synchronize #4239
  • Feb 20 23:24
    Aaronontheweb opened #4239
  • Feb 20 23:14
    Aaronontheweb commented #4234
  • Feb 20 22:52
    Aaronontheweb commented #4234
Arjen Smits
@Danthar
Problem is, you never know when you are done. So running this could kill your cluster :P because you;d end up continually spamming it with identify messages.
But it you could tweak it with clear end-conditions, or be able to restrict it parts of your cluster only. It could be the basis of a nice tool.
Bartosz Sypytkowski
@Horusiath
@Lejdholt it's a very good notice.
could you set that as an issue on github?
Lejdholt
@Lejdholt
Was hoping it was me who didn't understand ;P. But yes, I'll do that.
Bartosz Sypytkowski
@Horusiath
@eyantiful since you can send message through cluster in multiple ways, you need to be more precise. There are few various examples here i.e. cluster section from core repo and cluster web crawler
Lejdholt
@Lejdholt
@Horusiath here is the new issue akkadotnet/akka.net#1894
Jeff Cyr
@JeffCyr
@Lejdholt @Horusiath I think Unhandled(object msg) is called somewhere else in ReceiveActor
eyantiful
@eyantiful
@Horusiath sorry for the minimalism.
I have a custom serializer (ProtoBuf.Net) for type Message.
Message has (among others) IActorRef property for the initiator actor.
In the samples you mentioned the default serializer is used as far as i can tell.
Might be ISurrogated interface which should be surrogated?
I guess the question is more is passing IActorRef around good practice?
In a low-latency application what is the overhead of the resolving for each message?
Lejdholt
@Lejdholt
@JeffCyr If I want to log handled messages (commands) to a message store in my ReceiveActor without doing it in every receive function, how would I do that? I thought I could use AroundReceive for this, guess not. Feels a bit inconsistent but I think i'm missing something.
Jeff Cyr
@JeffCyr
@Lejdholt Do you expect an actor to receive a lot of unhandled messages? Why not log every messages?
Lejdholt
@Lejdholt
@JeffCyr No but I dont want to store commands that wasn't handled. Storing commands are for followup, what command resultet in that event, through correlationids and causationids
Artur Karbone
@ArturKarbone
Is there a more advanced way to control ITellScheduler? Cron-like for instance. Currently ITellScheduler provides initial delay and iterval.
I want something like once at 2AM during workdays, stuff like that. Thanks
Lejdholt
@Lejdholt
logging commands to a "normal" log is already done in the parent actor.
Jeff Cyr
@JeffCyr
@ArturKarbone Not sure if this is production ready, but I think you are looking for https://github.com/akkadotnet/Akka.Quartz.Actor cc @maxim-s
Artur Karbone
@ArturKarbone
@JeffCyr i think this is what i need. Thanks
Bartosz Sypytkowski
@Horusiath
@eyantiful in order to serialize IActorRefs, serializer must support surrogates (both Wire and JSON.NET do), otherwise you'd need to pass it i.e. string determining path to an actor, and then resolve it by yourself.
passing IActorRef is good, if used when necessary. Also how low-latency do you mean?
eyantiful
@eyantiful
@Horusiath we should support 15k concurrent msgs in under 100ms.
When you say resolving do you mean ActorSelection?
Jeff Cyr
@JeffCyr
@eyantiful Are you able to batch messages? Akka.Remote cannot handle 150K msg/sec
We are working on increasing the performance of Akka.Remote in v1.5
eyantiful
@eyantiful
@JeffCyr are you talking from single node? the figures are for the cluster as a whole.
@JeffCyr Im currently POC to see how far can we go with minimum nodes in order to asses cluster size...
Jeff Cyr
@JeffCyr
@eyantiful Yes I meant for a single node, I made a benchmark with two nodes on the same machine on loopback, I could get ~6K msg/sec
On v1.5 we were at 100K msg/sec for the same test, and there were still room for improvements
eyantiful
@eyantiful
@JeffCyr Default serializer change ?
Bartosz Sypytkowski
@Horusiath
@eyantiful actor system on a single machine (8 cores) can serve around 20-27mln msg/sec - this can be ofc slowed significantly by things such as persistence, but it also points how important local affinity of actors is
Bartosz Sypytkowski
@Horusiath
also for communication between nodes, take a look at Wire - it supports everything, default akka serializer should support and has quite good performance - you can see some comparison here
Vagif Abilov
@object
I get exception while executing TakeSnapshot command for persistence actors implemented in F#:
"Unable to cast object of type 'Akka.Serialization.WireSerializer' to type 'Akka.Serialization.NewtonSoftJsonSerializer'."
System.InvalidCastException: Unable to cast object of type 'Akka.Serialization.WireSerializer' to type 'Akka.Serialization.NewtonSoftJsonSerializer'.
at Akka.Persistence.FSharp.FunPersistentActor`3.OnCommand(Object msg)
at Akka.Persistence.UntypedPersistentActor.ReceiveCommand(Object message)
at Akka.Persistence.UntypedPersistentActor.Receive(Object message)
at Akka.Actor.ActorBase.AroundReceive(Receive receive, Object message)
at Akka.Persistence.Eventsourced.<ProcessingCommands>b__90_0(Receive receive, Object message)
at Akka.Persistence.Eventsourced.AroundReceive(Receive receive, Object message)
at Akka.Actor.ActorCell.ReceiveMessage(Object message)
at Akka.Actor.ActorCell.Invoke(Envelope envelope)
I inspected Akka code and apparently this line fails:
let serializer = UntypedActor.Context.System.Serialization.FindSerializerForType typeof<obj> :?> Akka.Serialization.NewtonSoftJsonSerializer
Bartosz Sypytkowski
@Horusiath
@object which version of Akka.FSharp are you using?
Vagif Abilov
@object
1.0.7
Jeff Cyr
@JeffCyr
@eyantiful Yes I was using Wire
Bartosz Sypytkowski
@Horusiath
ok, this is a bug
Vagif Abilov
@object
I have configured Wire as serializer, and as you can see that it casts to Newtonsoft.Json
Bartosz Sypytkowski
@Horusiath
I thought, we removed that line some time ago
Vagif Abilov
@object
So the workaround is to get rid of this line and compile from sources?
Zetanova
@Zetanova
This GC Collections test of PerfUtil for Gen0-2 looks interesting
Bartosz Sypytkowski
@Horusiath
@object yes, cause this line was part of workaround, we've made for json.net not being able to properly deserialize some of the f# types
Vagif Abilov
@object
I see. Should I create an issue for that or you will take care of this?
Bartosz Sypytkowski
@Horusiath
please set an issue, I have a limited time for last few months and I could forget that
Vagif Abilov
@object
OK. Should I submit a PR if this is only about removing the line? (If the fix requires a bigger effort, I am afraid I am too new to internals to handle it quickly).
Bartosz Sypytkowski
@Horusiath
as you'll see this is not only a single line
but you could play with it anyway
Vagif Abilov
@object
Yes I already see it's not a single line. But I'll see what I can do.
Bartosz Sypytkowski
@Horusiath
Akka.FSharp API is small, and part of responsible for serialization hack is even smaller
Vagif Abilov
@object
Further investigating F#/Wire persistence problem. It's not only Akka.Persistence.FSharp but also Akka.FSharp that has expectations about JSON.NET as the serializer.
And there is tryDeserializeJObject that is dependent on Newtonsoft.Json.Linq.JObject etc.
But I am not able to provoke an error if I get rid of this stuff and replace with general Akka.Serializer type and FromBinary method call.