You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My working theory is that for the system to resolve the hard faults and allow the process message queues to drain the messaging process needs more sleep time, ie CSecondSleep needs to be longer (at least as long as a timeslice?) or CMaxTries needs to be bigger (which would just result in more busy waiting).
I've been able to address the issue for the moment by making CSecondSleep = 500. A better hack might be some form of Nagleing or a HardFault notification.
Parallel.ForEach<Integer>( ... ).NumTasks( System.CPUCount ).Execute( ...)
api.I've noticed that once I get above 50% physical memory and hard faults begin to happen, ERROR_NOT_ENOUGH_QUOTA is thrown inside
OmniThreadLibrary/OtlContainerObserver.pas
Lines 331 to 354 in f74c63c
My working theory is that for the system to resolve the hard faults and allow the process message queues to drain the messaging process needs more sleep time, ie
CSecondSleep
needs to be longer (at least as long as a timeslice?) orCMaxTries
needs to be bigger (which would just result in more busy waiting).I've been able to address the issue for the moment by making
CSecondSleep = 500
. A better hack might be some form of Nagleing or a HardFault notification.Possibly related: #63
The text was updated successfully, but these errors were encountered: