SI
SI
discoversearch

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 : Intel Corporation (INTC)
INTC 36.34-0.1%Dec 23 3:59 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Timothy Liu who wrote (150467)11/29/2001 9:53:56 PM
From: kapkan4u  Read Replies (1) of 186894
 
The P4 decoder passes uops to the execution engine directly while building a new trace. In this mode P4 operates like a PIII with a single decoder. So if P4 ID is running at 2.0GHz and PIII's IDs are running 1.0GHz the speed of decode should be about the same.

P4 has higher branch mispredict penalty, but it also has twice (2.0GHz) as fast OOO execution engine and four times as fast (4.0GHz) add operations.

So if P4's ID is running at 2.0GHz one would expect P4 to be no more than say 30% slower than a 1.0GHz PIII.

I have no idea what the relative performance on this code would be, but I think sooner or later someone will try it.

Kap
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext