<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to measure Performance by using High Resolution Timer in Visual C++?</title>
	<atom:link href="http://weseetips.com/2009/03/31/how-to-measure-performance-by-using-high-resolution-timer-in-visual-c/feed/" rel="self" type="application/rss+xml" />
	<link>http://weseetips.com/2009/03/31/how-to-measure-performance-by-using-high-resolution-timer-in-visual-c/</link>
	<description>Gold mine of Visual C++ tricks!</description>
	<lastBuildDate>Thu, 12 Jan 2012 15:10:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Ryan</title>
		<link>http://weseetips.com/2009/03/31/how-to-measure-performance-by-using-high-resolution-timer-in-visual-c/comment-page-1/#comment-13693</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Mon, 16 May 2011 03:02:05 +0000</pubDate>
		<guid isPermaLink="false">http://weseetips.com/?p=969#comment-13693</guid>
		<description>My guess is it can&#039;t stop at exactly 3 seconds because the CPU clock cycle couldn&#039;t land exactly on 3 seconds, but it landed close. The clock cycle is based on the processor speed (1hz = 1second) and its a fixed time. There are so many clock cycles that you would think it could land on 3sec, but then you have to keep in mind the superscalar architecture and the pipeline, and if it was even possible to land on 3 sec. So many factors.</description>
		<content:encoded><![CDATA[<p>My guess is it can&#8217;t stop at exactly 3 seconds because the CPU clock cycle couldn&#8217;t land exactly on 3 seconds, but it landed close. The clock cycle is based on the processor speed (1hz = 1second) and its a fixed time. There are so many clock cycles that you would think it could land on 3sec, but then you have to keep in mind the superscalar architecture and the pipeline, and if it was even possible to land on 3 sec. So many factors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jijo.Raj</title>
		<link>http://weseetips.com/2009/03/31/how-to-measure-performance-by-using-high-resolution-timer-in-visual-c/comment-page-1/#comment-299</link>
		<dc:creator>Jijo.Raj</dc:creator>
		<pubDate>Wed, 15 Apr 2009 04:39:04 +0000</pubDate>
		<guid isPermaLink="false">http://weseetips.com/?p=969#comment-299</guid>
		<description>Hello marko,

GetTickCount() returns elapsed time in milliseconds. And if you need more accurate timing, then use - QueryPerformanceCounter().

Thanks for the comments and keep watching...

Regards,
Jijo.</description>
		<content:encoded><![CDATA[<p>Hello marko,</p>
<p>GetTickCount() returns elapsed time in milliseconds. And if you need more accurate timing, then use &#8211; QueryPerformanceCounter().</p>
<p>Thanks for the comments and keep watching&#8230;</p>
<p>Regards,<br />
Jijo.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marko</title>
		<link>http://weseetips.com/2009/03/31/how-to-measure-performance-by-using-high-resolution-timer-in-visual-c/comment-page-1/#comment-298</link>
		<dc:creator>Marko</dc:creator>
		<pubDate>Tue, 14 Apr 2009 19:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://weseetips.com/?p=969#comment-298</guid>
		<description>You can use GetTickCount() for high resolution timers.</description>
		<content:encoded><![CDATA[<p>You can use GetTickCount() for high resolution timers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

