CPU buying help
- NeoQuixotic
- Master Procrastinator
- Joined: Tue May 01, 2001 7:30 pm
- Status: Lurking in the Ether
- Location: Minnesota
- Contact:
CPU buying help
To help anyone who is going to ask about what CPU to buy and curious about the actual performance, I thought I should point out a very good link. It lists all major CPUs from 1995 to early 2005, and benchmarks them all in gaming, video and audio encoding, applications, and synthetic situations. The article is in 2 parts thus the two links. Part 2 contains the benchmark results. Enjoy! ^_^
Part 1
http://www.tomshardware.com/cpu/20041220/index.html
Part 2
http://www.tomshardware.com/cpu/20041221/index.html
Part 1
http://www.tomshardware.com/cpu/20041220/index.html
Part 2
http://www.tomshardware.com/cpu/20041221/index.html
- the Black Monarch
- Joined: Tue Jul 09, 2002 1:29 am
- Location: The Stellar Converter on Meklon IV
- RootHubController
- Joined: Sat Aug 07, 2004 6:47 pm
Easy. The EE has too long a pipeline. The pipeline would be optimal for a 5GHz proc, but instead, it's on a 3.4, and requires redundant instruction sets to accomplish work that could have been handled already.the Black Monarch wrote:I guess it's pretty sad that in a few benches, a 3.4 GHz Prescott on a 200mhz system bus with DDR-400 whipped a 3.46 GHz Extreme Edition on a 266mhz system bus with DDRII-533.
...just how the hell did that happen, anyway?
- NeoQuixotic
- Master Procrastinator
- Joined: Tue May 01, 2001 7:30 pm
- Status: Lurking in the Ether
- Location: Minnesota
- Contact:
Looking at the VOB to XviD benchmarks, my poor system with a 2.53 Ghz P4 at 533 mhz fsb (actually 133 mhz) and PC800 RDRAM would be longer than the listed 2.53 ghz P4 benchmark at 4:09. That means I'm running two times slower than the new P4s and AMD 64 FX-55 at 2:23 and 2:32! However, who can just throw away ~$1000 to the new processors? I can't, I'll tell you!
However, on most benchmarks my computer (a Dell, lol) still is plenty fast enough. I say if you have anything above 2.5 ghz (or AMD equivalent), stick with it for another year or 6 months at least. I think I can wait a couple more minutes for a video to encode and a .rar file to compress. Is a 2 minute (or less) speed boost or 200 more fps in Quake 3 worth $1000? Not really, unless you're a speed freak or working with gigantic files to compress 24/7, 365 days a year. Ok, I'm ranting, sorry. I just hate seeing people buy a new processor/video card/ram every month just because "it's faster". I'm just trying to say don't waste your money on a new cpu/computer for a performance boost you probably won't notice in most situations.
However, on most benchmarks my computer (a Dell, lol) still is plenty fast enough. I say if you have anything above 2.5 ghz (or AMD equivalent), stick with it for another year or 6 months at least. I think I can wait a couple more minutes for a video to encode and a .rar file to compress. Is a 2 minute (or less) speed boost or 200 more fps in Quake 3 worth $1000? Not really, unless you're a speed freak or working with gigantic files to compress 24/7, 365 days a year. Ok, I'm ranting, sorry. I just hate seeing people buy a new processor/video card/ram every month just because "it's faster". I'm just trying to say don't waste your money on a new cpu/computer for a performance boost you probably won't notice in most situations.
- Otohiko
- Joined: Mon May 05, 2003 8:32 pm
Yea, and in many cases you have to add a new motherboard into the equation, such as in mine.
I'd like to switch to a 64-bit processor eventually, but frankly, I can't swing the cost of processor+motherboard (and my current 2400+ is practically at the limit of my motherboard's supported clock speed).
I'll probably wait at least a year or a year and a half before I even think of upgrading this.
Thanks for the useful info though
I'd like to switch to a 64-bit processor eventually, but frankly, I can't swing the cost of processor+motherboard (and my current 2400+ is practically at the limit of my motherboard's supported clock speed).

I'll probably wait at least a year or a year and a half before I even think of upgrading this.
Thanks for the useful info though

The Birds are using humanity in order to throw something terrifying at this green pig. And then what happens to us all later, that’s simply not important to them…
- RootHubController
- Joined: Sat Aug 07, 2004 6:47 pm
- Scintilla
- (for EXTREME)
- Joined: Mon Mar 31, 2003 8:47 pm
- Status: Quo
- Location: New Jersey
- Contact:
Well, they <i>are</i> also better at doing the same old 32-bit operations, aren't they?RootHubController wrote:I'll be more inclined to do it when there's software that supports and exploits the full advantages fo the 64-bit architecture. Yes, it's backwards compatible, but you're not recieving any benefits.I'd like to switch to a 64-bit processor eventually
- Kalium
- Sir Bugsalot
- Joined: Fri Oct 03, 2003 11:17 pm
- Location: Plymouth, Michigan
From what I understand, this is often the case.Scintilla wrote:Well, they <i>are</i> also better at doing the same old 32-bit operations, aren't they?RootHubController wrote:I'll be more inclined to do it when there's software that supports and exploits the full advantages fo the 64-bit architecture. Yes, it's backwards compatible, but you're not recieving any benefits.I'd like to switch to a 64-bit processor eventually
Besides, RootHubController seems unaware that there are already quite stable 64-bit OSs. They just aren't Microsoft OSs.
-
- is
- Joined: Tue Jul 23, 2002 5:54 am
- Status: N͋̀͒̆ͣ͋ͤ̍ͮ͌ͭ̔̊͒ͧ̿
- Location: N????????????????
There's one point he still has: even OSes that work in 64-bit mode on x86-64 processors haven't yet taken full advantage of the system. Oh, sure, you get nice things like the ability to easily address >= 1GB of RAM without hacks or slowdown, and recent compilers are able to schedule code effectively specifically for x86-64, but I've only seen a couple of applications that actually take advantage of the system.Kalium wrote:From what I understand, this is often the case.Scintilla wrote:Well, they <i>are</i> also better at doing the same old 32-bit operations, aren't they?RootHubController wrote:I'll be more inclined to do it when there's software that supports and exploits the full advantages fo the 64-bit architecture. Yes, it's backwards compatible, but you're not recieving any benefits.I'd like to switch to a 64-bit processor eventually
Besides, RootHubController seems unaware that there are already quite stable 64-bit OSs. They just aren't Microsoft OSs.
One thing I'd like to do is benchmark two Gentoo setups running on the same Athlon64 machine and see how much of a difference I get out of running typically CPU-intensive operations that tend to move around a lot of data. I'm running Gentoo x86-64 right now but without any sort of reference point I can't say much about it.
-
- is
- Joined: Tue Jul 23, 2002 5:54 am
- Status: N͋̀͒̆ͣ͋ͤ̍ͮ͌ͭ̔̊͒ͧ̿
- Location: N????????????????
I should clarify that.trythil wrote:There's one point he still has: even OSes that work in 64-bit mode on x86-64 processors haven't yet taken full advantage of the system. Oh, sure, you get nice things like the ability to easily address >= 1GB of RAM without hacks or slowdownKalium wrote:From what I understand, this is often the case.Scintilla wrote:Well, they <i>are</i> also better at doing the same old 32-bit operations, aren't they?RootHubController wrote:I'll be more inclined to do it when there's software that supports and exploits the full advantages fo the 64-bit architecture. Yes, it's backwards compatible, but you're not recieving any benefits.I'd like to switch to a 64-bit processor eventually
Besides, RootHubController seems unaware that there are already quite stable 64-bit OSs. They just aren't Microsoft OSs.
On a 32-bit processor, each process can address a maximum of 4GB (2^32) of memory. However, some operating systems enforce a kernel/user separation for each process's virtual address space. I know Linux does this, and I'm pretty sure Windows does, too.
On Linux the default is a 1GB/3GB split; i.e. the first 1GB is kernel address space, and the 3GB is user address space. As the kernel can access only up to 1GB of memory in this scheme, you are effectively limited to 1GB of physical RAM. (Those are the terms I'm used to thinking in, thus the >= 1GB statement.) With a 2GB/2GB split it's a 2GB limit. And so forth.
I suppose what I wrote would have been better phrased "you get freaking huge address pointers", and anyone interested in 64-bit would have immediately understood the implications of that.