- Dec 8, 2002
- 531
- 0
- 0
Guys I've read two articles and from reading on here I gather the P3 is faster then the p4 mhz for mhz. What is the reason behind this, none of the articles I read did a good job explaining it.
I haven't really looked into it myself, but it's true EXCEPT for video/audio manipulation (A/V Editting mainly)....in those cases the P4 spanks all.
Originally posted by: fkloster
I haven't really looked into it myself, but it's true EXCEPT for video/audio manipulation (A/V Editting mainly)....in those cases the P4 spanks all.
FACTS:
1) the HIGHEST clock P4 (3.06) FLOGS the HIGHEST clock P3 (1.0) by an EXTREME margin in every test...
2) the LOWEST clock P4 (1.3) FLOGS the LOWEST clock P3 (.45) by an EXTREME margin in every test...
...any questions?
Originally posted by: fkloster
I haven't really looked into it myself, but it's true EXCEPT for video/audio manipulation (A/V Editting mainly)....in those cases the P4 spanks all.
FACTS:
1) the HIGHEST clock P4 (3.06) FLOGS the HIGHEST clock P3 (1.0) by an EXTREME margin in every test...
2) the LOWEST clock P4 (1.3) FLOGS the LOWEST clock P3 (.45) by an EXTREME margin in every test...
...any questions?
Correct. Initially the P3 was faster than the P4 clock for clock. But the P4 has improved dramatically since the 1.4 GHz days:Originally posted by: Diable
A P3 is probably faster then a P4 of the same speed on old non-SSE2 enhanced code. But if the app has any SSE2 code the P4 will smack the P3 silly.
Originally posted by: dexvx
Common myth. The p3 cannot scale very high, due to its low FSB bandwidth. If you scale P3's to 3Ghz, I doubt it will perform as well as a 3.06HT P4. But then again if you scale a P4 to ~1Ghz, it'll probably get beat by a p3 1Ghz simply because it cannot take advantage of its high bandwidth FSB.
The initial reviews of the p4 1.5Ghz put it marginally faster than the P3 1Ghz, and it left everyone with a very sour image to the P4's performance. Since that time there has been numerous optimizations for the P4, compiler wise. Simply recompiling the program using the SSE2 intel extensions can yield a substantial boost in app speed. Couple that with the 512KB cache, 533/800 FSB, PC1066 RDRam, and its quite fast per clock.
Excellent post, dullard.Originally posted by: dullard
Correct. Initially the P3 was faster than the P4 clock for clock. But the P4 has improved dramatically since the 1.4 GHz days:Originally posted by: Diable
A P3 is probably faster then a P4 of the same speed on old non-SSE2 enhanced code. But if the app has any SSE2 code the P4 will smack the P3 silly.
1) The long P4 pipleline meant the IPC was really bad due to these mispredictions. This was the major reason that the P3 was faster clock for clock. However the faster the clockspeed the less time penalty you have for the branch mispredictions. And we all know the P4 clockspeed has doubled since the early days. Thus this problem is greatly diminished.
2) The P4 now has double the cache. This also increases the P4 IPC.
3) The P4 has gone from 400 MHz to 533 MHz fsb. Soon it will be at 800 MHz fsb. All this means the P4's IPC keeps increasing.
4) Better memory, better motherboards, better optimizations, etc have occured since the early P4 days.
5) Hyperthreading which will soon move down to the slower P4s will give a good boost on average to the P4's IPC.
6) Software is now optimized for the P4 - including SSE2 code.
All these reasons now mean that for many programs the P4 is actually now faster than the P3 clock for clock. 5LiterMustang, I bet those articles you read were old and didn't include the things I listed above. The picture has changed dramatically.
I have a 1.2 Ghz Tualatin Celeron (which is basically an "improved" PIII @100FSB). However, it really doesn't perform too well until you raise the FSB to approach 133Mhz. Mine is at 1.5Ghz and is very comparable performancewise to the (old) 1.8 Ghz P4 (still no "need" to change my 8500 either).Originally posted by: alkemyst
I haven't really looked into it myself, but it's true EXCEPT for video/audio manipulation (A/V Editting mainly)....in those cases the P4 spanks all.
I am going to run a 1.4-S Tualatin for a while I think....my Radeon 8500 handles games smoothly and with enough eye candy they are cool.
I even stopped overclocking my Radeon and it was still nice.
Originally posted by: ElFenix
Originally posted by: dexvx
Common myth. The p3 cannot scale very high, due to its low FSB bandwidth. If you scale P3's to 3Ghz, I doubt it will perform as well as a 3.06HT P4. But then again if you scale a P4 to ~1Ghz, it'll probably get beat by a p3 1Ghz simply because it cannot take advantage of its high bandwidth FSB.
The initial reviews of the p4 1.5Ghz put it marginally faster than the P3 1Ghz, and it left everyone with a very sour image to the P4's performance. Since that time there has been numerous optimizations for the P4, compiler wise. Simply recompiling the program using the SSE2 intel extensions can yield a substantial boost in app speed. Couple that with the 512KB cache, 533/800 FSB, PC1066 RDRam, and its quite fast per clock.
and it still gets pwned! by a pentium m
Originally posted by: fkloster
I haven't really looked into it myself, but it's true EXCEPT for video/audio manipulation (A/V Editting mainly)....in those cases the P4 spanks all.
FACTS:
1) the HIGHEST clock P4 (3.06) FLOGS the HIGHEST clock P3 (1.0) by an EXTREME margin in every test...
2) the LOWEST clock P4 (1.3) FLOGS the LOWEST clock P3 (.45) by an EXTREME margin in every test...
...any questions?
Originally posted by: dexvx
Originally posted by: ElFenix
Originally posted by: dexvx
Common myth. The p3 cannot scale very high, due to its low FSB bandwidth. If you scale P3's to 3Ghz, I doubt it will perform as well as a 3.06HT P4. But then again if you scale a P4 to ~1Ghz, it'll probably get beat by a p3 1Ghz simply because it cannot take advantage of its high bandwidth FSB.
The initial reviews of the p4 1.5Ghz put it marginally faster than the P3 1Ghz, and it left everyone with a very sour image to the P4's performance. Since that time there has been numerous optimizations for the P4, compiler wise. Simply recompiling the program using the SSE2 intel extensions can yield a substantial boost in app speed. Couple that with the 512KB cache, 533/800 FSB, PC1066 RDRam, and its quite fast per clock.
and it still gets pwned! by a pentium m
You didnt appear to have read my statement. I reiterated that the P3 was FSB bound. The 512KB cache on the tualatins help, but when you're approaching a higher ratio, it is nullified. Pentium-M enjoys the benefit of a quad pumped P4 bus.