Way back in Ignite 2.8 we ran into an issue with continuations from Ignite
Async method calls that meant our code could continue to run on an Ignite
striped thread pool thread, with sometimes bad results.
At the time the pattern suggested was to use a .ContinueWith()
continuation, like this:
await _cache.PutAsync(key, value).ContinueWith(t => { },
CancellationToken.None, TaskContinuationOptions.None,
TaskScheduler.Default);
to ensure that the continuation after the PutAsync occurred on a .Net
thread pool thread. This worked with no further bad results.
A little while ago we upgraded to 2.13, and I note in this link (
https://ignite.apache.org/docs/latest/key-value-api/basic-cache-operations)
that the default behaviour has been changed.
My reading of this is that the example above can now be changed to:
await _cache.PutAsync(key, value);
with the continuation occurring on a .Net threadpool thread by default. Is
that correct?
This will allow us to remove the (quite a few) .ContinueWith() statements
which do add a layer of overhead on async calls.
Thanks,
Raymond.
--
<http://www.trimble.com/>
Raymond Wilson
Trimble Distinguished Engineer, Civil Construction Software (CCS)
11 Birmingham Drive | Christchurch, New Zealand
raymond_wil...@trimble.com
<https://worksos.trimble.com/?utm_source=Trimble&utm_medium=emailsign&utm_campaign=Launch>
