... and when you replace the hard drive with a "SATA2 DDR2 HyperDrive5", the swap memory bottleneck practically disappears. http://www.hyperossystems.co.uk/
Nope... It's the kind of solution you get when the developer has more time available and wants the code to consume a different resource; more Heap than Stack. It is slower because you are managing your own container in the Heap and not leveraging the PUSH/POP of registers, but this is outweighted by the massive advantage of being able to consume as much Heap memory as the OS will give it. It will aslo make the code more compatiable / portable to run in different modes; everything from 8bit EPROMs running in virtual memory to the latest 64bit OSs... all you really have to do is port and compile without really having to answer the question of "Will the compile parameters be big enough? (stack size)".
Ahh... We all speak at least 2 languages...
0 Geek; 'cause its the only real way to express the perception.
1 Native; 'cause its the only way to know when the fridge is going to be restocked;-)
... and while it doesn't, the quality of the site will remain a victim to internet marketers who are building up their page rank. Follow the links and you will find it's a trail, offsite.
Slashdot Mirror
Can you add a moderation option for "Whoosh ..."
Give the Squirrels lasers. I for one welcome our new Laser wielding Squirrel Overlords.
Aihh ... then we're all in 'grement, too be sure.
... and when you replace the hard drive with a "SATA2 DDR2 HyperDrive5", the swap memory bottleneck practically disappears. http://www.hyperossystems.co.uk/
Wasn't that a Futurma episode? (No TV)
Nope ... It's the kind of solution you get when the developer has more time available and wants the code to consume a different resource; more Heap than Stack. It is slower because you are managing your own container in the Heap and not leveraging the PUSH/POP of registers, but this is outweighted by the massive advantage of being able to consume as much Heap memory as the OS will give it. It will aslo make the code more compatiable / portable to run in different modes; everything from 8bit EPROMs running in virtual memory to the latest 64bit OSs ... all you really have to do is port and compile without really having to answer the question of "Will the compile parameters be big enough? (stack size)".
Ahh ... We all speak at least 2 languages ... ;-)
0 Geek; 'cause its the only real way to express the perception.
1 Native; 'cause its the only way to know when the fridge is going to be restocked
... and while it doesn't, the quality of the site will remain a victim to internet marketers who are building up their page rank. Follow the links and you will find it's a trail, offsite.