Clustering

2»

Comments

  • cracker_jackmaccracker_jackmac Join Date: 2002-11-04 Member: 6891Members, Constellation, Reinforced - Shadow
    <!--QuoteBegin--Jeb+Feb 18 2003, 09:59 PM--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (Jeb @ Feb 18 2003, 09:59 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> I think linux should share the load between the 2 processors fine. (with the kernel patched.)
    <!--QuoteEnd--> </td></tr></table><span class='postcolor'> <!--QuoteEEnd-->
    it already does that w/o a patch....you have to patch it if you want CPU affinity

    <!--QuoteBegin--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->I have always felt that if MS did its job properly and balanced the load between both processors, then people shouldn't ever need to assign anything to one cpu.<!--QuoteEnd--></td></tr></table><span class='postcolor'><!--QuoteEEnd-->

    That is not the case. Sometimes for stability, you don't want a rouge process crashing your system....assigning it a single proc limits is "crashivness" (like my new word?).

    This is especially useful for program testing. You system can run on one CPU, while your lack of programing skills shine on your other 100.1% CPU
Sign In or Register to comment.