c# - Service Fabric Actor Timers Performance Implications -

we thinking of potentially using service fabric actor timers sort of ttl management service. has potential have 100 hundreds of thousands of actor timers @ time. concerned overhead of having many actor timers running @ time there not seem sort of documentation regarding actor timers performance implications or underlying mechanisms. guidance appreciated.

from know, actor's timer uses lightweight 'system.threading.timer' under hood, creating along delegate has code dispatch call toward 'wake-up' callback when time comes. , seems dispatch happens other incoming request have, i'd couple classes delegate cost of having sf actor timer.

of course, if need perform lot of work within timer's callback lock actor, depends on how many requests blocked , how fast leave callback.