We are running an application on a 4100 with 4.0D that is consuming a
tremendous amount of memory. Each invocation of the program results in 4
other processes being created. The 5 together have a resident size of about
75Mb and we need to have at least 30 running at any one time. Need less to
say we have to find a way to get the footprint down on these apps since we
certainly cant scale this way. This is all homegrown code, and it is all
built with shared object libs. What we dont know is what exactly is in these
executables that is making them so big and is there a way to verify that the
shared libs are really being shared. It doesn't appear to be the case
according to our programmers.
Are there any commands or tools that will give us visibility into what these
monstrous applications are made of and how they are being run or that they
are indeed sharing code?
Thanks
John Hergert
Volkswagen of America
Received on Thu May 20 1999 - 19:24:31 NZST