Welcome to the Lounge

Super Lloyd wrote:

Need more buzzwords though!

    public class TimedBlock : IDisposable
    {
        Stopwatch stopwatch;

        public TimedBlock([CallerMemberName] string name = null)
        {
            Name = name;
            stopwatch = new Stopwatch();
            stopwatch.Start();
        }
        public string Name { get; set; }
        public TimeSpan Elapsed { get { return stopwatch.Elapsed; } }

        public virtual void Dispose()
        {
            stopwatch.Stop();
            Trace.WriteLine($"TimedBlock({Name}, {Elapsed})");
        }
    }
    public class TimeCriticalBlock : TimedBlock
    {
        TimeSpan max;

        public TimeCriticalBlock(TimeSpan max, [CallerMemberName] string name = null)
            : base(name)
        {
            this.max = max;
        }

        public override void Dispose()
        {
            base.Dispose();
            if (Elapsed > max)
            {
                var msg = $"code too slow, {Name} took {Elapsed}.";
                Trace.Error(msg);
#if DEBUG
                if (Debugger.IsAttached)
                    Debugger.Break();
#endif
            }
        }
    }

Super Lloyd wrote:

Log are also in a file.. But it's easier to read in the console (just click on it) and easier to update the server (just stop, copy files, and restart)

Sander Rossel wrote:

The using statement certainly makes it better

using (new TimedBlock())
{
   // Your time critical code here.
}

Super Lloyd wrote:

This way, if the code slow down more than acceptable... the developer got an automatic reminder by the system while debugging!