This object reports the longest single continuous run time, in milliseconds, that this process has held the CPU. Admins check this to spot processes that monopolize the CPU for unusually long stretches, which can delay other tasks and cause latency-sensitive protocols to misbehave. A routing process showing 250 milliseconds would be far less concerning than one showing 5000 milliseconds, which suggests it's blocking other work for multiple seconds at a time.