Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.
The PIII 1.4S was a server chip and had double the cache and performed pretty well for it's time; the Athlon 1.4 Thunderbird wins hands down if you live in a cold climate and can use the heat. The XP1600+ ran at the same speed if I remember correctly and was more efficient.
I'm not sure but I wouldn't be surprised if a Tulatin PIII 1.4 beats the Thunderbird 1.4, especially at non-gaming tasks. IIRC the PIII didn't hit those clock speeds until much later than the Thunderbird and by then had other architectural improvements that shot up performance per clock. I think the tulatins may even be built on a smaller die process, plus they had SSE support where the thunderbird didnt. I believe the coppermine PIII were a more direct competitor to the thunderbird.
With the XP series AMD added SSE support and improved performance per clock so I'd imagine that would take the lead
Someone please englighten me on the details 🙂 I love comparing old tech.
The P3 Tualatin 512K was a beast for the time, it was just overpriced and impractical for home users (not to mention tualatin-compatible Socket 370 boards usually meant buying a new one even for owners of relatively recent P3 ~1ghz builds. Tualatin was .13mu process tech, and it allowed for 512k of full-speed cache, whereas the older Coppermine was .18mu just like Thunderbird and was limited to 256k L2.
I would put them this way .. P3 1.4S (512K L2) slightly faster than Athlon 1400 (much much much cooler though), and about equal in most circumstances to 1600+.
The 1400 Thunderbird was a furnace, and nearly as bad/desperate as the P3 1.13 Coppermine. They just shouldn't have attempted it. I've only seen one in the wild that worked at stock clocks with the stock cooler, and not for very long. I had one and ended up having to downclock it to 1050mhz just to get it stable under a thermalright XP-90 and 5000rpm fan, lol. That was also the bad old days of the non-IHS chips that cracked quite easily just installing a heatsink and following proper directions for heatsinks that were labeled Socket A/462 compatible. God forbid you try to install a golden orb, hah. *crack*. I had much much better luck with the Athlon XP chips in terms of reliability/durability, and they performed really well.
Athlon XP 1st gen ~> P3 Tualatin 512k > Athlon Thunderbird > P3 Tualatin 256k / Coppermine 256k > Athlon K7 (off-die L2 at a slow ratio compared to core clock) > P3 Katmai (off-die L2 at 1/2 core speed).
The AXP vs. Tualatin 512k is hard to compare due to the use of model ratings. The AXP clock for clock was slightly faster, but the model ratings matched up more closely to hypothetical 256k l2 P3 chips that didn't exist (eg; AXP 1600 = or better than P3 1600mhz coppermine), even if the model ratings weren't officially a direct comparison at all.
The 1600+ is in a league of its own being that overclocking it to 2ghz should be no problem at all. I have four of them laying around. FYI, Thunderbird came before the XP, and it was a piece of crap thermally.
The only computer I ever had that acted like a space heater had a Thunderbird in it.
Yeah the P3 1.4GHz "S" Tualatin 512K came way late and required new motherboards but performed comparably to even the first Socket 423 Pentium 4's with SDRAM.
I'm still running one in my "server" machine on an ASUS TUSL2-C and that chip won many server designs of its time.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.