It does this.
info: Orleans.Runtime.Catalog Before collection#2: memory=13MB, #activations=3, collector=<#Activations=2, #Buckets=1, buckets=[1h:59m:47s.591ms->2 items]>. info: Orleans.Runtime.Catalog 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.
memoryto tell it to not collect.
IPersistentState<T>instances into the constructor of a
Grainthat they are loaded from the persistence store concurrently during activation? Looking at the code it appears a
PersistentStateBridge<T>is created for each
IPersistentState<T>instance and those subscribe to the
SetupStatelifecycle stage. Inside the
LifecycleSubjectthese seem to be started concurrently for a given stage and awaited for using
Task.WhenAll. I'm hoping this indeed the case because splitting up state for a single grain is a nice way of reducing the amount of data that needs to be persisted if a logical partitioning is present. The example I have is configuration data and runtime data, where configuration data is only required on activation to configure the work to be done, and runtime data is stored more frequently as work is performed. That gives you a performance boost on the write side so I am hoping the read side on activation is concurrent so there is a read benefit to be had too.