使用 C# 检索系统正常运行时间
有没有一种简单的方法可以使用 C# 获取系统的正常运行时间?
Is there a simple way to get a system's uptime using C#?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
有没有一种简单的方法可以使用 C# 获取系统的正常运行时间?
Is there a simple way to get a system's uptime using C#?
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(10)
我有点晚了,但另一种简单方法是使用GetTickCount64 函数,该函数从 Windows Vista 开始可用,并且不会像 GetTickCount 那样溢出:
I'm a bit late, but another simple way is to use the GetTickCount64 function, which is available starting with Windows Vista and does not overflow as GetTickCount does:
System.Environment.TickCount 获取自此以来的毫秒数系统已重新启动。
但请注意,它是 Int32,并且会在 24.9 天后溢出并变为负值。 请参阅 MDSN 文档上的注释。
System.Environment.TickCount gets the number of milliseconds since the system was restarted.
Beware though that it is an Int32 and will overflow after 24.9 days and will become negative. See the remarks on the MDSN docs.
根据任务管理器,我的机器的正常运行时间为
58 天 17 小时
。 我浏览并尝试了这里的每个答案,快速的答案稍有偏差(大约 1-3 分钟,但正常运行时间超过 58 天):最后两个,使用 PerformanceCounter 或使用 ManagementObject,总是在同一秒内作为 Windows 任务管理器(只需相信我的话,或者使用下面的代码自行尝试)。 根据结果,我将使用
ManagementObject LastBootUpTime
方法,因为它比PerformanceCounter
快得多,但与任务管理器相比仍然非常准确。请注意,在打印时间之前,我确实从每个方法中减去了当前经过的时间,但整个过程的运行时间不到 2 秒,因此无论如何都不能通过不正确地计算执行时间来解释时间偏移。 这是我使用的代码:
My machine has an uptime of
58 days 17 hours
according to Task Manager. I went through and tried each answer here and the fast ones are off by a little bit (~1-3 minutes roughly, but over 58 days of uptime):The last two, using PerformanceCounter or using ManagementObject, are always within the same second as Windows Task Manager (just have to take my word for it, or try it yourself with the code below). Based on the results I am going to use the
ManagementObject LastBootUpTime
method because it's drastically faster than thePerformanceCounter
but is still perfectly accurate when compared to Task Manager.Note that I did subtract the current elapsed time from each method before printing the times, but the whole thing takes less than 2 seconds to run so the time shift can't be explained by improperly accounting for execution time anyway. Here's the code I used:
比 System.Environment.TickCount 更精确且更大,不涉及操作系统可怕的性能计数器、WMI 或本机调用:
Precise and bigger than
System.Environment.TickCount
, not involving OS horrific perf counters, WMI or native calls:如果您使用的是更高版本的 .NET(Core 3.0/.NET 5.0 或更高版本),则
Environment
类现在具有 TickCount64 属性。这不会受到
TickCount
属性的环绕问题的影响,您也不必求助于 P/Invoke 来获取该值。If you are using a later .NET version (Core 3.0/.NET 5.0 or above), then the
Environment
class now has a TickCount64 property.This doesn't suffer from the wrap-around issues of the
TickCount
property, nor do you have to resort to P/Invoke to get the value.最简单且正确的方法是
The simplest and proper way to do this is
简单,不,但可以做到:
Simple, no but it can be done:
我知道问题既古老又已解决,但我能想到的最有效的解决方案就是使用 Enviroment.TickCount 属性,它返回自系统启动以来的毫秒数:
此解决方案比公认的答案快得多。
I know question is both old and solved, but the esiest solution I can tink of is just using the Enviroment.TickCount property, which returns the number of millisecounds since the system started:
This solition is a lot faster than the accepted answare.
[编辑:] 现在完全没有必要了,因为 .net 已经有了
Environment.TickCount64
(或Stopwatch
类)。 请忽略。(唯一的)正确答案,[编辑:很久以前在一个很远的地方:]
使用 32 位定时器非常危险,并且除了有限的使用之外,很容易出错。
我不确定 NativeMethods 类的内容何时被添加到 .net 中,但确实如此。 您肯定希望避免 P/Invoke 开销。 做这个:
[edit: ] Completely unnecessary now that .net has
Environment.TickCount64
(or theStopwatch
class). Please disregard.The (one and only) correct answer, [edit: a long time ago in a place far far away: ]
Using the 32-bit timer is incredibly dangerous, and prone to error for all but limited use.
I'm not sure when the NativeMethods class stuff was added to .net, but it was. You definitely want to avoid P/Invoke overhead. Do this: