Real world experience with Intel CPUs
A reader posted the following based on his many years of experience:
I live in the “Real World” not the “Benchmark World.” The problem I have with the Intel CPU is that it is real fast until it reaches “Critical Mass” where it suddenly stops. (Five minutes to open Outlook, I couldn’t connect with Terminal services either.) AMD, however, slows proportionally to the load, and when dealing with an Outlook memory leak putting the CPU at 100% usage recently, I was still able to remote in and fix the problem.
I fully agree. I had used Intel servers before, in a lot of situations, the server got overloaded, reaching 100% CPU utilisation, when that happened, it was impossible to login remotely. I had to call the datacenter and had the locked up Intel server rebooted. I never had similar problems with Opterons.
In one of Bob Colwell's stanford lectures, he admitted that the Intel CPU design uses an instruction scheduling algorithm that often enters a kind of loop which it takes a long long time to get out. When that happens, the Intel CPU would appear locked up.