On Fri, Apr 11, 2008 at 12:21 PM, Jürgen Keil <[EMAIL PROTECTED]> wrote: > > And another case was an attempt to use "xsltproc(1)" on a > > big xml file, this time on an amd64 x2 machine with 4GB of > > memory, using zfs, and the xsltproc process had grown to > > use > 2GB of memory. Again heavy disk trashing, and I > > didn't had the impression that the arc cache did > > shrink enough to prevent that thrashing. > > It looks like this, in top:
prstat can give more accurate info on Solaris, fyi. > > load averages: 0.01, 0.02, 0.05 > 21:11:47 > 75 processes: 74 sleeping, 1 on cpu > CPU states: 99.4% idle, 0.1% user, 0.5% kernel, 0.0% iowait, 0.0% swap > Memory: 4031M real, 108M free, 2693M swap in use, 1310M swap free > > PID USERNAME LWP PRI NICE SIZE RES STATE TIME CPU COMMAND > 7587 jk 1 60 0 2430M 2306M sleep 0:25 0.24% xsltproc Only 124M of the xsltproc process is paged - The rest is resident, but there is 2693M of swap in use. It appears that something other than your xsltproc is paged out. AFAIK, the ARC should not page, so what else is using that memory? Your ARC + xsltproc are only equal to 2754M. There's something else on your system consuming 3862M. Before you ran the process, what did things look like, memory wise? Also keep in mind that /tmp is an in memory filesystem. Things written there will use physical memory, or page out if required. Also, could you sort the output by memory usage? "prstat -s rss" and "prstat -s size" will sort by resident size or total image size. -B -- Brandon High [EMAIL PROTECTED] "The good is the enemy of the best." - Nietzsche _______________________________________________ opensolaris-discuss mailing list [email protected]
