It is scheduled on the default .NET threadpool, so it is as inexact as Task.Delay (which is used under the covers)
If there is a high load on the threadpool, the task might finish later than planned.. that is, there is no guarantee that it will execute exactly at the millisecond youd expect
@Horusiath not exactly but I suppose that once I get a working model together it could be used that way. Currently I use ES with my aggregates using the file system and SQL server which works but it does not scale easily. So I am stretching out the file system and SQL with Cassandra and putting
Resizable Pool Consistent Hash Router in front of that. If there is something that I can be of assistance with I would be happy to help.