Hi there, with all that great ways of caching data - nscache, nsv... - in AOLserver and a strategy of caching as much data as possible, at what point would you say the size of the processes becomes a "problem" for the application running AOLserver? I don't think of physical RAM and swap, I think of AOLserver and starting new threads, using ns_eval to propagate changes from APIs to all other processes, responding to requests and similar things.
What are sizes you usually see on your systems? This is something on my machine, for example: PID USER PRI NI SIZE RSS SHARE STAT CPU MEM TIME COMMAND 26591 nsadmin 17 0 70944 68M 2616 S 0.0 13.6 0:50 nsd 26594 nsadmin 15 0 70944 68M 2616 S 0.0 13.6 0:00 nsd 26595 nsadmin 20 0 70944 68M 2616 S 0.0 13.6 0:00 nsd 26596 nsadmin 15 0 70944 68M 2616 S 0.0 13.6 0:21 nsd 26601 nsadmin 15 0 70944 68M 2616 S 0.0 13.6 0:00 nsd 26602 nsadmin 15 0 70944 68M 2616 S 0.0 13.6 0:06 nsd (and it runs without problems so far). Bernd.
