To: Joseph Pareti who wrote (74460 ) 2/25/1999 12:32:00 PM From: Jim McMannis Respond to of 186894
RE:"from Tom:I have to say that I am a bit disappointed by the K6-3, since it only really shines when running integer operations. Applications with floating point calculations as e.g. 3D-games, voice recognition, 3D-rendering and video compression do only run fast enough if optimized for 3DNow!, Unfortunately AMD wasn't able to do a great job in convincing software developers to do decent optimizations for 3Dnow!, so that the majority of software does still not take advantage of AMD's floating point SIMD instructions, although this instruction set is available for almost 9 months now. "... ---- Actually, I think that was a pretty fair assesment however no one expected the K6-III to suddenly have a more powerful FPU than the K6-2. The K7 will address that. 3DNow! had a 9 month lead but as I've said before, AMD didn't do enough. They stuck pretty much to games and left some few holes for Intel to fill with apps like Photoshop, Natuarally speaking and Mpeg2 encoding. Not only that but Intel went a step further by actually sending engineers to rework code to optimize speed as well as writing to take advantage of KNI. This resulted in a real big jump in the "made for Intel" benchmarks. Why AMD didn't work with Photoshop, Dragon (I hear there is an IBM 3dNow optimized voice recognition program) and some of the companies that write Mpeg encoding programs as well as those who write .wav editors, is beyond me. These are very FPU intensive programs so you'd think AMD would have gone after them to make up for the weaker performance of their chips on these programs. If AMD would contact me I'd give them a list. Still, when you consider the number of apps that really benefit from KNI, doesn't seem like a good value at this time. Kind of reminds me of MMX, but then again, KNI was originally named MMX2, then, Katmai instructions, KNE, now I see it's refered to as SSE...so who else is confused. The CPUID thing is the much bigger issue. I suggest you read the posts from Jeff Fox. A great voice of reason on that issue and he certainly can't be accused of being anti-Intel. Jim