To: wanna_bmw who wrote (52664 ) 8/27/2001 7:13:18 PM From: Dan3 Respond to of 275872 Re: When an optimized app is used You are confusing "an optimized app" with an optimized benchmark. There are almost no examples of actual applications, such as serving data, encoding video, compiling code, etc. where a P4 1.7 is faster than an Athlon 1.2. Meanwhile virtually the entire installed base of millions of programs (un-"optimized" code) is faster on an Athlon. What do exist are some artificial "benchmarks" that were carefully coded to avoid the many instructions that P4 can't handle well. These aren't optimized X86 applications, they are optimized P4 benchmarks. We need to see, for example, how Microsoft Media encoder (tuned to avoid P4's weaknesses) compares with some of the more standard media encoding software (that was compiled with the goal of encoding media, rather than working around P4's weaknesses). Maybe Microsoft Media encoder, using "optimized" code really is an optimized application. The interesting thing to do would be to compare its performance with other software with the same functionality that was neither aided nor crippled by the need to accommodate P4's various warts and failings. The hard thing, of course, is to to ensure that equal quality output comes from each program (when encoding anything, it's not hard to pump out ugly garbage at high speed, or high quality sound and images at low speed, what's tough is to do both at once). So far, at least, whenever the task is defined as a real application, doing real work - serving data, compiling code, etc. Athlon is faster. When the task is defined as completing an Intel optimized benchmark, sometimes the P4 comes out ahead.