So I have a new gaming PC now; my old gaming PC will become a file server. I have 4x500gb drives to get started (all from the old PC) but I'm rearranging some parts into my girlfriend's Shuttle.
Complexify!
CURRENT SHUTTLE
Processor.................2.66 Intel P4 533mhz
Memory....................758mb DDR400
Graphics...................XFX 6800GS 128MB
Storage....................80GB WD Caviar
Motherboard............Shuttle SN45G
CURRENT OLD GAMING
Processor................3.0 Intel P4 800mhz
Memory...................2GB DDR400
Graphics..................ATI X1950 Pro 256MB
Storage...................4x500GB SATAII
Motherboard...........Gigabyte 8KNXP
I'm moving the RAM, Processor, and Video card to the Shuttle. I have 2 choices with the file server. I can either replace the processor in the FS with the 2.66 (non-HT) P4 478, buy a cheap 2.8ghz (HT) P4 478, or upgrade to a motherboard with a 775 socket and use my 3.6ghz P40 (from a Compaq X6000 notebook). This means, however, using DDR2.
Investment with
old Shuttle proc: $0
Investment with
new 2.8ghz P4: $30 (refurb)
Investment with
new mobo/RAM: $58-70 (new mobo) $38-41 (new RAM)
The new mobo will have onboard video so I don't need to buy a video card as well (and for overall reduction in power consumption).
So, should I spend $100+ for a 3.6ghz single core, or deal with a slower 2.6 or 2.8ghz single core and sub 1GB RAM?
Posts
Maybe an idea of what you will be sharing and the number of users accessing it would be helpful to.
The PC will be running XP Pro - I may look into Linux, but for now, I'll keep things familiar. Mainly, the content is HD rips; 1 drive is filled with music, the other 3 will be filled with mostly HD content, various programs, and random personal backups.
I would ultimately like to use this to stream the HD content, which is why I'm contemplating the upgrade for the faster proc. However, I don't know if processing power matters when all the HD content is doing on the file server is streaming/accessing, not necessarily displaying.
Streaming a video file should basically be the same as sending a file over the network (if it's not, then whoever wrote the program that's requesting the file is doing things *very* badly, or doing something strange/fancy). Not much processing power is required at all.
Maximum PC did a great write up on this a couple issues ago, if you're wondering.