System.Threading.Timer Sample Code (VB.NET)

I consider this to be best practice.

This sample codes requires the knowledge of multi-threading.

1.) It examines two models.

1.1.) Single timer multiple tasks model.

1.2.) Multiple timer objects model.

2.) Reentrancy Issues:

For both model, reentrancy will still happen. In fact, reentrancy cannot be avoided, it can only be mitigated.

2.1.) Try to use system.threading.timers and asynchronous processing. System.timers.timer are more for synchronous processing.

2.2.) Design the program in such that if previous scheduled task is not yet completed, ignore current task schedule and come back later.

3.) CPU Utilization:

Both models have the about the same CPU utilization, with single timer model suffers slightly higher CPU.

The bottleneck is happening at refreshing text at 'System.Windows.Forms.Label'

The more GUI refreshes is made, the high CPU utilization and the slower data gets to be displayed real time.

4.) Benefits of Single Timer Multiple Tasks Model:

Improve manageability, single point of troubleshooting, single point of view.

4.1.) Reduce the possibility of deadlock.

4.2.) Reduce the possibility of exceptions.

5.) Conclusion

5.1 Both models are workable.

5.2 It is not necessary to deploy the single timer multiple tasks model, which will give rise to more bottlenecks and more CPU utilization. Using multiple timer objects proves to be more optimized.

5.3) The most important thing is to mitigate Reentrancy.

Download the (sample code)VB.NET Visual Studio 2008 SP1

Other References:

Also refer to 'System.Timers.Timer Vs System.Threading.Timer'

And 'System.timers.timer hung or hangs'