>i'm okay with the atom suffering a little bit (odd how far down the food >chain one can get 64 bits!), i'm actually more concerned about >being punshed severely for forking on a beefy but busy machine. >the atom is just my test mule.
don't worry about it too much at this point. i need allocation units smaller than 2Mb myself, and 32 bits come to that. it's easy to think of ways to address that, but one thing at a time. it might be best to look at the things that are not well done first, before considering things that we (probably) know how to do from experience. also, the applications that ron wants to run are typically fat and greedy, aren't compositions of processes (in the usual sense), and are long-running and relatively static once they start (at the moment). some other potential applications on similar machines, for services such as file serving, will typically build up a service pool and recycle that.
