I found some material about pennmush, it claims it is memory based unlike tinymux which is disk based, the FAQ was about running it on '90-s old hardware like 8 MB total ram and 40-50 MHz CPU, and some kind of old *nix, it says pennmush utilizing only 5-10% of the cpu and using 4 MB ram on a fully operational mud with tons of softcode looping all the time.
The faq is all about how to write smart and efficient softcode to squeeze out everything from the puny machine. Like creating the room at the very moment when a player enters the room and destroying it immediately after the player left the room, using command queues, keeping only essential stuff in the master room. Other parts of the faq discuss the issues when *nix begin to swapping causing lag, etc...
... do I have to care about such things on my modern hardware?
I have a spare 24/7 machine for pennmush, P4 3 GHz, 1 GB ram 80 GB hdd and fast net access.
The faq is all about how to write smart and efficient softcode to squeeze out everything from the puny machine. Like creating the room at the very moment when a player enters the room and destroying it immediately after the player left the room, using command queues, keeping only essential stuff in the master room. Other parts of the faq discuss the issues when *nix begin to swapping causing lag, etc...
... do I have to care about such things on my modern hardware?
I have a spare 24/7 machine for pennmush, P4 3 GHz, 1 GB ram 80 GB hdd and fast net access.