AH!! But you all forget that windows itself will gobble up all the memory it can get it's greedy little kernel on. Don't believe me? put 128meg in your machine then reboot with 1gig...trust me the more memory you have the faster it will run. I thought 1gig would be overkill when I upgraded to it but now I see that if I put 2gig in it would still not be running as fast as it could. It's not the apps that need the memory its the friggin overhead in there OS."LUG's are AA for computer junkies"Tux Rocks
"Programs are generally written with single processor systems in mind, and therefore cannot run any better when the extra resources exist."
This is an OS problem not an architecture problem. Linux kernals already exist that can "SMP enable a non SMP" program through kernal ajustments across hundreds of "nodes" with the program none-the-wiser. AKA "openmosix"(opensource) or "mosix"(proprietary)
Slashdot Mirror
AH!! But you all forget that windows itself will gobble up all the memory it can get it's greedy little kernel on. Don't believe me? put 128meg in your machine then reboot with 1gig...trust me the more memory you have the faster it will run. I thought 1gig would be overkill when I upgraded to it but now I see that if I put 2gig in it would still not be running as fast as it could. It's not the apps that need the memory its the friggin overhead in there OS."LUG's are AA for computer junkies"Tux Rocks
"Programs are generally written with single processor systems in mind, and therefore cannot run any better when the extra resources exist." This is an OS problem not an architecture problem. Linux kernals already exist that can "SMP enable a non SMP" program through kernal ajustments across hundreds of "nodes" with the program none-the-wiser. AKA "openmosix"(opensource) or "mosix"(proprietary)
Uh... Everything you just said is pretty much exactly what they did for the Athlon-64 to get people to transition to 64 bit.