>so optimizing for gaming will also improve server and database performance
um.. i could be wrong, but arnt we talking about a graphics system here? and optimizing a graphics system for gaming would do absoultly nothing for DB performance.
have you ever tried dual/multi head? every person who has knocked a multi moniter setup that i know in person was a changed person after they used a rig with multi moniters on it. personnaly, i run 3 moniters (4 if you count the TV), 19" samsung 900 IFT with a pair of 17" 700 IFTs flanking it. the tv under windows is running in matrox's 'DVDMax' mode where it will grab any video played and display it on the tv full screen. a g400 agp and pair of voodoo3s drive the rig. its nice to be able to get crap that you're not currently paying attention to but need to keep an eye on off the main screen but within a glance (ie : server moniters, xmms, irc). and it totaly kicks ass for web dev stuff.:)
ive been running x11amp since version.9 (.7 didnt like SMP boxes..), it has crashed (its still in dev, of couse its gonna crash), but for it to take down your entire system? sounds like a bug in OSS, or are you running x11amp as root?
(if i really wanted to be an ass, i could blame it on a shitty OS that allows a user process to crash the box, but ive never ran *BSD, so im just gonna keep my mouth shut on it)
ok, this is just one of my whacked out ideas, but it is a proven fact that history repeats. I could be wrong, but didnt life all out suck right before the reenaissance? now look at today's world, the school killings, the big businesses, all this legal copyright crap, and the impending y2k problem. maybe all this bs that is going on is a good thing, a sign of things to come? who knows, we might be on the edge of a revolution in thinking, a new renaissance?
first off, id like to say, you will not get performace boosts from apps that are not coded for SMP (threaded), they will go the same (maybe a bit faster due to other processes being on a diffrent cpu) as if they were on a single cpu box. thus you could say that dual PII 233 would run slower then a PII 450.
also, some programs are not very happy being run on a SMP box (ie : X11amp version.9, mpg123, mpegtv, xlib)
but, SMP has its merits. i have caught myself many times saying "damn i love SMP" while playing quake and compiling a new kernel, or encoding mp3s.
also, smp acts a floodgate for out of control processes, for a process on smp cannot steal all your cpu power, just on one of them.
so, if you are a gamer, get the UP PII 450. if you are a power user who does 50 things at once, id go with a SMP PII 233 or whatever, or you could get the SMP mainboard, and only 1 cpu, and get the second one later (dual 450s... *drool*)
ps. Q3a does not support SMP AFAIK at this time, john c played around with the graphics engine being threaded, and only got a !5% speed boost after some major tweeking, but i think i read he will play around with it some more later after the code becomes more stable
sounds like the drive was in pio mode... hdparm -d /dev/ and if i was a betting man, id say it would come out with 0
>so optimizing for gaming will also improve server and database performance
um.. i could be wrong, but arnt we talking about a graphics system here? and optimizing a graphics system for gaming would do absoultly nothing for DB performance.
have you ever tried dual/multi head? every person who has knocked a multi moniter setup that i know in person was a changed person after they used a rig with multi moniters on it. personnaly, i run 3 moniters (4 if you count the TV), 19" samsung 900 IFT with a pair of 17" 700 IFTs flanking it. the tv under windows is running in matrox's 'DVDMax' mode where it will grab any video played and display it on the tv full screen. a g400 agp and pair of voodoo3s drive the rig. its nice to be able to get crap that you're not currently paying attention to but need to keep an eye on off the main screen but within a glance (ie : server moniters, xmms, irc). and it totaly kicks ass for web dev stuff. :)
(This is biased, you have been warned)
.9 (.7 didnt like SMP boxes..), it has crashed (its still in dev, of couse its gonna crash), but for it to take down your entire system? sounds like a bug in OSS, or are you running x11amp as root?
ive been running x11amp since version
(if i really wanted to be an ass, i could blame it on a shitty OS that allows a user process to crash the box, but ive never ran *BSD, so im just gonna keep my mouth shut on it)
ok, this is just one of my whacked out ideas, but it is a proven fact that history repeats. I could be wrong, but didnt life all out suck right before the reenaissance? now look at today's world, the school killings, the big businesses, all this legal copyright crap, and the impending y2k problem. maybe all this bs that is going on is a good thing, a sign of things to come? who knows, we might be on the edge of a revolution in thinking, a new renaissance?
first off, id like to say, you will not get performace boosts from apps that are not coded for SMP (threaded), they will go the same (maybe a bit faster due to other processes being on a diffrent cpu) as if they were on a single cpu box. thus you could say that dual PII 233 would run slower then a PII 450.
.9, mpg123, mpegtv, xlib)
also, some programs are not very happy being run on a SMP box (ie : X11amp version
but, SMP has its merits. i have caught myself many times saying "damn i love SMP" while playing quake and compiling a new kernel, or encoding mp3s.
also, smp acts a floodgate for out of control processes, for a process on smp cannot steal all your cpu power, just on one of them.
so, if you are a gamer, get the UP PII 450. if you are a power user who does 50 things at once, id go with a SMP PII 233 or whatever, or you could get the SMP mainboard, and only 1 cpu, and get the second one later (dual 450s... *drool*)
ps. Q3a does not support SMP AFAIK at this time, john c played around with the graphics engine being threaded, and only got a !5% speed boost after some major tweeking, but i think i read he will play around with it some more later after the code becomes more stable