Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Advanced Micro Devices - Moderated (AMD) -- Ignore unavailable to you. Want to Upgrade?

To: Ali Chen who wrote (87552)	8/23/2002 8:08:54 PM
From: TGPTNDR	Read Replies (1) \| Respond to of 275872

Ali, Thanks for the SYSmark 2002 post. Interesting. I'd like to actually see a run, but it sounds like they're using an automated script (Like the Mercury interactive product.) to 'push the buttons' of the underlying applications.( I certainly hope they're not relying on somebody sitting there mouse clicking. ) I got a kick out of the 'Trial run option'. Gives a fellow a chance to load ram before things really get going. -tgp

To: Ali Chen who wrote (87552)	8/24/2002 1:39:49 AM
From: Petz	Respond to of 275872

I disagree with your conclusion that Sysmark doesn't measure completion times. In fact, I think it starts timing the instant the menu selections are made, because that is the "user response" portion. Whats different compared to, say ZD Winbench is that most of the time the computer is doing absolutely nothing. It only measures applications for very short time intervals needed to respond to each task. Winbench may have 1000s of tasks run by artificially stuffing keystrokes into the application. The screen goes crazy as these thousands of commands are executed and the total runtime measured. The idea of pausing between each task is not bad, but it requires much greater accuracy in measuring the task completeion time. I think there's technical issues with how Bapco does that. Its just not very easy to measure a millisecond on a PC accurately. So, not only are the task selections and weightings biased, but there are problems with the measurement process that cause anomalies like a 3 GHz computer running everything twice as fast as a 2 GHz. Petz