Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 18:38
    nkosi23 commented #7120
  • 18:34
    krasin-ga commented #7099
  • 18:30
    nkosi23 commented #7120
  • 18:28
    nkosi23 commented #7120
  • 18:26
    nkosi23 commented #7120
  • 18:25
    nkosi23 commented #7120
  • 18:25
    nkosi23 commented #7120
  • 18:24
    nkosi23 commented #7120
  • 18:22
    drakeforte5 commented #7120
  • 18:21
    drakeforte5 commented #7120
  • 18:12
    SebastianStehle commented #7120
  • 16:43
    nkosi23 commented #7120
  • 15:40
    ReubenBond commented #7099
  • 15:22
    krasin-ga commented #7110
  • 15:02
    krasin-ga commented #7099
  • 14:59
    drakeforte5 commented #7120
  • 14:59
    drakeforte5 commented #7120
  • 14:58
    drakeforte5 commented #7120
  • 14:58
    drakeforte5 commented #7120
  • 14:57
    drakeforte5 commented #7120
Tom Nelson
@Zeroshi
im not sure sure what it does exactly and i would like to figure that out
COCPORN
@COCPORN
It seems to me like service fabric is dead or dying.
Tom Nelson
@Zeroshi
i think fabric supports all of azure
COCPORN
@COCPORN
I have worked with it.
Tom Nelson
@Zeroshi
whats the point of it versus orleans?
COCPORN
@COCPORN
Yes, in that way I am being hyperbolic. But starting off a new project that isn't part of the infrastructure of Azure it seems less supported than, say, AKS at this point.
I am not going to "badmouth" Orleans here. Not that I ever would. But Service Fabric seems to want to solve another problem altogether.
The same way I like to run Orleans on a Kubernetes cluster, I think it makes sense to run Orleans on SF.
Tom Nelson
@Zeroshi
yeah, it seems like it does thinks that k8 does
and monitors while performing health checks
COCPORN
@COCPORN
I would spend 5-19 minutes with the SF actor model before dismissing it.
Tom Nelson
@Zeroshi
lol
COCPORN
@COCPORN
I wrote this for fun back in the days: https://github.com/COCPORN/SimpleFabric
As a stepping stone if you wanted to create a service based on virtual actors that would easily transition to SF.
Turns out Orleans starts up in a second and it's the same code you're developing with that goes into production.
Tom Nelson
@Zeroshi
thats really cool. thank you for sharing
sorry i had a meeting
COCPORN
@COCPORN
No worries. I just start yapping some times.
Tom Nelson
@Zeroshi
why did you default the actor to 30 min? just random?
also, why isnt there an orleans' book?
COCPORN
@COCPORN
I don't understand what you mean by 30 minutes. The repo I shared is meant for exploratory coding at best, so if that is what you're referring to it is probably random.
Tom Nelson
@Zeroshi
one thing i really need to get up to speed on is the the release pipeline for orleans
COCPORN
@COCPORN
Let's do the meetup then!
I will be the heckler, you can be the voice of reason.
Tom Nelson
@Zeroshi
yeahm you just had it hard coded. i wasnt sure if your actors generally cover 90% of the needs in 30 min
i already have it on my calendar!
i ported it to linkedin as well
COCPORN
@COCPORN
In related news, I still haven't gotten a good (in my opinion) response to my idea of only releasing grains on configurable memory pressure.
Tom Nelson
@Zeroshi
define "memory pressure"
COCPORN
@COCPORN
As in: I have a bunch of grains, and they default to being retired after 2 hours of idling.
But also: I have 14GB of RAM on this computer. And retiring them when I have 10GB available is not sensible.
Tom Nelson
@Zeroshi
ah, got it
COCPORN
@COCPORN
So you can set a limit for when you start retiring grains to, say, 6GB.
Everything else will work the same.
It is literally just an if-statement in the codebase.
Tom Nelson
@Zeroshi
yeah, i like that. use a sorted list based on max idle time
COCPORN
@COCPORN
No, you don't even need to do that. It already buckets grains, so it knows which ones to retire.
Tom Nelson
@Zeroshi
i had to do that for sql cache
i meant the silo's list
COCPORN
@COCPORN
Just don't even start that process if you have a lot of memory available. This is my suggestion.
Tom Nelson
@Zeroshi
good idea
i was thinking of it as a trigger based on memory usage
then cleanup x amount of sorted list that is owned by the silo
COCPORN
@COCPORN
It runs the eviction of old grains on a timer.
Tom Nelson
@Zeroshi
yeah, but thats 1 trigger, the other can be the memory amount
COCPORN
@COCPORN
info: Orleans.Runtime.Catalog[100507]
      Before collection#2: memory=13MB, #activations=3, collector=<#Activations=2, #Buckets=1, buckets=[1h:59m:47s.591ms->2 items]>.
info: Orleans.Runtime.Catalog[100508]
      After collection#2: memory=13MB, #activations=3, collected 0 activations, collector=<#Activations=2, #Buckets=1, buckets=[1h:59m:47s.582ms->2 items]>, collection time=00:00:00.0086615.
It does this.
You could literally just have an if statement on memory to tell it to not collect.
Tom Nelson
@Zeroshi
yup, you are right
COCPORN
@COCPORN
I am not sure if I am right. It is hard to combine with drinking and yapping, my two favorite hobbies after drinking and yapping.
Anyhows, I am heading out. Nice to talk to you so far.