.NET Thread Pool is exhibiting delays of 13.3251887s. This can indicate .NET Thread Pool starvation, very long .NET GC pauses, or other runtime or machine pauses.

Question

.NET Thread Pool is exhibiting delays of 13.3251887s. This can indicate .NET Thread Pool starvation, very long .NET GC pauses, or other runtime or machine pauses.

Closed this issue 3 months ago · 2 comments

hi

Can using File.Delete in the timer lead to the following error?

.NET Thread Pool is exhibiting delays of 13.3251887s. This can indicate .NET Thread Pool starvation, very long .NET GC pauses, or other runtime or machine pauses.

this.RegisterGrainTimer(SaveKeys, false, new()
{
DueTime = TimeSpan.FromSeconds(10),
Period = TimeSpan.FromSeconds(10),
Interleave = true,
KeepAlive = true
});

Answer 1 · 2024-10-06T17:12:45.000Z

That sounds plausible, depending on where the file is stored (eg a network drive) and the level of concurrency - how many such timers are there?

Answer 2 · 2024-10-06T18:05:04.000Z

yes it is NFS storage.
1400 grain with one timer per 10 second.