You have some flex, of course, but generally the closer you get to the metal, the better.
VB has options for changing the CPU, but it has to software-emulate anything it can't do natively; whereas something like 90% of native stuff can be handed directly to the CPU. The less overhead you have, the smoother everything runs. To make up an example; if you set it up as a new high-end 128-bit processor, and say 50% of the cpu functions had to be emulated; then you install Linux on it, which detects the newer cpu, and configures itself to use as much of the cpu as it can. At that point, you're really hammering the software emulation. If you set it to Pentium 4, and Linux sets itself up to run as fast as it can on that CPU, then a larger share of what the OS does can be done on he hardware, without overhead. -- -- You received this message because you are subscribed to the Linux Users Group. To post a message, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit our group at http://groups.google.com/group/linuxusersgroup References can be found at: http://goo.gl/anqri Please remember to abide by our list rules (http://tinyurl.com/LUG-Rules or http://cdn.fsdev.net/List-Rules.pdf) --- You received this message because you are subscribed to the Google Groups "Linux Users Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
