reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Douglas Service <dsop...@gmail.com>
Subject .NET Core Timmer issues
Date Fri, 02 Sep 2016 02:33:49 GMT
I am working on JIRA-1554 which replaces the C# System.Timers.Timer class
with System.Threading.Timer. Unfortunately only the version that takes 32
bit "due time" and "period" parameters is available in .NET Core (I
verified this on the .NET Core website) however the parameters passed to
the TimerStage class both in Java and C# are longs.

This still gives users a maximum timeout of 2^32/1000 = 4294967 seconds =
1193 hours = 49.7 days. Which seems like long enough for a REEF job.
Comments?

The documentation for the timer class says

The method specified for *callback* should be reentrant, because it is
called on ThreadPool
<https://msdn.microsoft.com/en-us/library/system.threading.threadpool(v=vs.110).aspx>
threads.
The method can be executed simultaneously on two thread pool threads if the
timer interval is less than the time required to execute the method, or if
all thread pool threads are in use and the method is queued multiple times.


Does anyone know what the original design requirements were for the the
TimerStage and RXTimerStage classes? A search on timer stage does not
reveal any usage of the classes in REEF.

Doug

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message