On Thu, 12 Feb 2009, Martin Bochnig wrote:
/usr/bin/top showed me that one of the 5 wget sessions I had started a week ago (for fetching opensolaris.org, sdlc.com/osol, genunix.org and a few LinUX mirrors) had grown to 2GB!!! And one day later it was 2.2GB. So I killed that wget pid and started the same wget (same dir / website) again. The four other wget processes were between "only" 122MB and about 250MB. So, one day later they had grown further, but here comes the absolute HAMMER: One top process was at 1340MB!!!
Your 'top' program obviously has some sort of bug but otherwise I don't see anything necessarily out of the ordinary in the top listings. Some releases of top work much better under Solaris than others. Top is a very handy tool but neither 'SIZE' or 'RES' is indicative of a problem. For example 'SIZE' is increased by simply memory mapping a file or device since it is based on the number of allocated virtual memory pages. Virtual memory pages may be shared between processes. RES is a bit more useful since it indicates the amount of those virtual memory pages which are mapped into RAM, but it is also misleading since pages may remain mapped into RAM due to lack of pressure for memory (from other processes) as well as pressure from memory from the running process. If you want to learn more about how memory is being used by a Solaris process, then see 'pmap'.
It does seem a bit unusual that any swap is used at all. Double check to make sure that you have not copied a bunch of large files to /tmp since /tmp comes out of the total memory/swap budget.
Perhaps the algorithm that 'wget' uses requires a lot of memory to keep track of things, or perhaps the version you are using has a memory leak.
Bob ====================================== Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ _______________________________________________ perf-discuss mailing list perf-discuss@opensolaris.org
