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 : Advanced Micro Devices - Moderated (AMD)
AMD 241.28-2.0%1:08 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Dan3 who wrote (74596)3/15/2002 8:27:26 AM
From: Joe NYCRead Replies (1) of 275872
 
Dan,

Hit rates will vary with code and data, but Athlon will have a substantially better hit rate than P4. Doubling the "wayness" of a cache is roughly equivalent to a 2 to 3 times size increase, so Athlon's 384K cache performs about as well as P4 with 750K to 1Meg cache. Which is probably the main reason Athlon does so well in server applications.

This part is something I am a little dubious about. You mentioned that Athlon can store more locations, but given smaller total cache, each location can store less data. There may be cases when you many locations to be cached (I guess heavily multithreaded application, but there are times when you don't, and having more data sitting in the cache will be an advantage.

I don't know where the trade-off is in real world applications, but my guess is in benchmarks, when usually a single task is being measured, P4 with more total L2 has an advantage.

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