Slashdot Mirror
Today's Best CPUs Compared... To a Pentium 4
Dr. Damage writes "How do current $74 CPUs compare to the $133 ones? To exclusive $1K Extreme Editions? Interesting questions, but what if you took a five-year-old Pentium 4 at 3.8GHz and pitted it against today's CPUs in a slew of games and other applications? The results are eye-opening." Note that this voluminous comparison is presented over 18 pages with no single-page view in sight.
The conclusion I made is that liberal arts majors have no business trying to convey technical information. (Jump to the conclusions page to verify that the author was a liberal arts major.)
I've been using a Pentium 4 3.0GHz-powered box as a MythTV frontend/backend for more than four years. It often records four high-definition over-the-air or FireWire MPEG-2 streams while playing back another.
For the first three years I used an Nvidia video card with Xv output to play the recordings at very good quality with 50-70% CPU usage. A year ago I moved to VDPAU, which gives me even better playback with under 5% CPU usage, and will do the same with h.264 recordings (generated by the Hauppauge HD-PVR, for example). Thanks to VDPAU, there's every possibility I'll be able to use the Pentium 4 box for another four years.
...and the fastest modern CPU is still not fast enough for another 2%.
45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
There's an easy way to thwart that advertising blackmail for users of Firefox: the AutoPager extension. Antipagination would probably still work for older versions of Firefox.
Speaking as a PS3 dev, the SPUs are very different to program for than a normal multi-core cpu (and you only get to use five and a half of them anyway, not 7).
On the flip side, everything based on UE3 (which is most big cpu-hungry multi-platform titles these days) is multithreaded to two or three significant threads: Game, rendering, and possibly physics (depending on physics engine used). None of them are SPU threads (though they may use the SPUs for some tasks), so PS3 performance isn't generally as good as the 360's, but in most games it's a non-issue as both platforms go over the 30 fps cap.
On PC, most UE3 games will run best on two cores, with anything above that being unnecessary.
Did anyone else notice how the Q9550 and Q9650 are absent from this article?
Probably the last thing Intel wants is these previous generation (and attractively priced) chips appearing in the "overall performance per dollar" chart on "Page 17 - The value proposition". Instead, we get a graph where only the i5 and i7 chips appear to perform well beyond any of the older options, but it's a carefully crafted illusion because the faster (and attractively priced) versions of those older chips weren't tested.
PJRC: Electronic Projects, 8051 Microcontroller Tools
AMD processors and the newer (i3, i5, i7) Intel processors have the memory (DRAM) controller built in. The ECC here is for the DRAM, I have no idea about internal cache. Google released a study a few months ago with various information about actual observed memory error rates... after a bit of crunching on their numbers, I came up with an expected 1/5 chance of a single random bit-flip over a 6-year lifespan, and a 1/3 chance of part of your memory going bad (and causing crashes, corruption, etc, if not caught with ECC) after a couple years.
I work on flight simulators and we DEPEND on multiple core processors to get everything done at once. What used to take multiple racks of computers can now be done on a single computer with dual quad-core CPUs.
You think IPC is slow on a single machine? Try using reflective memory across multiple computers. Of course we have to handle a bit more than your typical video game since we have to handle hundreds of buttons and switches from multiple crew member stations, night vision, FLIR and day TV cameras, as well as out the window displays.
Is this little jewel on page 14:
This to me is the most telling thing in the review. The bloat that has crept into the software made the same cpu take twice as long to render the same scene. This is why we have machines now that make the machines we used 10 years ago look stupid by the numbers, while they don't really offer that much of an improvement in experience due to the incredible amounts of software bloat eating all the extra resources available. This one little paragraph should make the people involved with POVray bow their heads in shame.