blocks|key|3791408|text|@Kogus:即使我在调试器外部运行(独立的应用程序。从命令提示符)，它仍然可能被操作系统抢占，并导致错误地测量我的应用程序所消耗的时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3791409|不是吗？|3791410|-AD|3791411|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

@Kogus: Even if i run outside debugger(standalone app. from a command prompt) it still could be preempted by OS and cause a incorrect measurement of the time consumed by my app.

Is'nt it?

-AD

blocks|key|1476102|text|我认为你在粒度上会有一些问题。请参阅类似的问题GetLocalTime()+API+time+resolution和Is+gettimeofday()+guaranteed+to+be+of+microsecond+resolution?|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1476103|此外，您可能希望查看包含timeit.exe+(类似于unix/linux上的time+)的Windows+Resource+Kits+Tools，以提供运行时间和处理时间。|style|CODE|1476104|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/49668/getlocaltime-api-time-resolution|1|https://stackoverflow.com/questions/88/is-gettimeofday-guaranteed-to-be-of-microsecond-resolution|2|http://www.microsoft.com/downloads/details.aspx?familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en^0|N|Y|0|1P|1M|1|0|13|4|1A|R|2|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]|$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@$A|11|B|12|F|G]]|9|@$A|13|B|14|1|15]]|C|$]]|$1|H|3|-4|5|6|7|16|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]|R|$5|K|L|M|C|$N|S]]]]

I think you are going to have some problems with the granularity. See similar questions <a href="https://stackoverflow.com/questions/49668/getlocaltime-api-time-resolution">GetLocalTime() API time resolution</a> and Is <a href="https://stackoverflow.com/questions/88/is-gettimeofday-guaranteed-to-be-of-microsecond-resolution">gettimeofday() guaranteed to be of microsecond resolution?</a>

Also, you may want to take a look at the <a href="http://www.microsoft.com/downloads/details.aspx?familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd&amp;displaylang=en" rel="nofollow noreferrer">Windows Resource Kits Tools</a> which include timeit.exe (similar to <code>time</code> on unix/linux) to give you elapsed and process times.

blocks|key|1475956|text|建议|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1475957|尝试在多CPU系统上运行。|1475958|entityMap^0|0|2|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

Suggestion

Try run on multi CPU systems.

blocks|key|3791363|text|1-在代码中添加一些调试日志(当然包括时间戳)，并在调试器之外运行它|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3791364|2-在调试器中再次运行|3791365|3-重复多次，以获得统计上有效的数据。|3791366|4-比较。|3791367|如果单机和调试器的平均执行时间有显著差异，那么您应该怀疑操作系统(或调试器钩子本身的开销...)。如果没有区别，那就不用担心了。|3791368|Edit0:显然，调试消息有其自身的一些开销。即使在从调试器运行时，您也可能希望将这些保留在代码中。这样，独立调试器和调试器都可以运行完全相同的代码。|3791369|Edit1:我误解了这个问题。我认为您担心的是，在调试期间，操作系统可能会比在正常执行模式下更频繁地中断您的应用程序。如果你想知道你的应用程序实际花费了多少时间，只需将所用的时间与任务管理器中的"CPU时间“进行比较。|3791370|Edit2:将为您的进程返回的时间与实际执行时间进行比较。不同之处在于CPU在其他人身上花费的时间。|3791371|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

1 - Put some debug logging in your code (include timestamps of course), and run it outside of the debugger

2 - Run again in the debugger

3 - Repeat many times, to get statistically valid data.

4 - Compare.

If there is a significant difference in the average execution time of the standalone vs. the debugger, then you are right to be suspicious of the OS (or the overhead of the debugger hooks themselves...). If no difference, then don't sweat it.

Edit0: Obviously the debug messages have some overhead of their own. You may want to leave those in the code even when you are running from the debugger. That way, both the standalone and the debugger are running the very same code.

Edit1: I misunderstood the question. I thought your concern was that --while debugging--, the OS might interrupt your app more frequently than in a normal mode of execution. If you want to know how much time your app actually spent working, just compare the time taken to the "CPU Time" in the Task Manager.

Edit2: Compare the time returned by <a href="http://msdn.microsoft.com/en-us/library/ms683223(VS.85).aspx" rel="nofollow noreferrer">GetProcessTimes</a> for your process to the actual execution time. The difference is the time spent by the CPU on somebody else.

blocks|key|5259477|text|最好的方法是使用专用的分析工具。外面有很多。我已经有几年没有在C中使用它了，希望其他人能给出更好的建议。由于您正在使用Visual+Studio2005，因此这可能是一个很好的起点：AQ，但我从未使用过它。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5259478|entityMap|0|LINK|mutability|MUTABLE|url|http://www.automatedqa.com/products/aqtime/^0|2J|2|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

The best way of doing this is a dedicated profiling tool. There are lots out there. I haven't used one for C for a few years, someone else will hopefully be able to give better advice. As you are using Visual Studio 2005 this might be a good place to start:
<a href="http://www.automatedqa.com/products/aqtime/" rel="nofollow noreferrer">AQ</a>, but I've never used it.

I am doing profiling of a C code in Microsoft VS 2005 on a Intel Core-2Duo platform. 
I measure the time(secs:millisecs) counsumed by my function. But i have some doubts about the accuracy of this measurement as the operating system will not continuously run my application, but instead schedule others apps/services in between the execution of my code.(Although i have no major applications running while i do the profile run, still windows will have lot of code of its own which it will run by preempting my app.). Because of all this i believe the profiling number(time taken by my app to run) is not accurate. 

So my question is there any way to find out the Operating system overheads, scheduling overhead on a typical windows system(I run Windows XP)e.g. if my applications says it ran for 60 milliseconds, out of that 60 msec, how much time really was used by my app. and how much time it was sitting idle, due to being pre-empted by some other task scheduled by the OS?

or 

Atleast is there any ball-park number to get such OS overhead, based on your experience you came across while doing something similar?

Operating System Overheads while profiling?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在Intel Core-2 2Duo平台上对Microsoft VS 2005中的一个C代码进行评测。我测量函数所用的时间(秒:毫秒)。但我对这种测量的准确性有一些怀疑，因为操作系统不会持续运行我的应用程序，而是在我的代码执行之间调度其他应用程序/服务。(虽然我在运行配置文件时没有运行主要的应用程序，但windows仍然会有很多自己的代码，它们将通过抢占我的应用程序来运行。)正因为如此，我认为

问评测时的操作系统开销？
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问评测时的操作系统开销？EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问评测时的操作系统开销？
EN