I'm building Sage on one of my SPARCs which does not have much RAM
(only 2 GB), though its enough to build Sage OK. But I noticed when
building the documenation, the memory usage is quite high.

This is the output from 'prstat' - the Solaris tool like 'top'.

   PID USERNAME  SIZE   RSS STATE  PRI NICE      TIME  CPU PROCESS/NLWP
  4191 drkirkby  476M  400M cpu1    50    0   0:35:17  50% python/1
 10783 drkirkby 4512K 4144K cpu0    58    0   0:00:00 0.1% prstat/1
   657 drkirkby 8320K 1880K sleep   59    0   0:00:36 0.0% sshd/1
  2451 drkirkby 8344K 2728K sleep   59    0   0:00:00 0.0% sshd/1
  2453 drkirkby 3000K 2448K sleep   59    0   0:00:00 0.0% bash/1
  4150 drkirkby 6464K 4896K sleep   59    0   0:00:00 0.0% python/1
  4124 drkirkby 1184K  976K sleep   59    0   0:00:00 0.0% tee/1
   289 root     2320K 1280K sleep  100    -   0:00:07 0.0% xntpd/1
    82 root     4216K 3032K sleep   59    0   0:00:03 0.0% nscd/26
    69 root     3256K 1376K sleep   59    0   0:00:03 0.0% picld/6
     7 root       11M 1504K sleep   59    0   0:00:05 0.0% svc.startd/13
    85 root     2488K  648K sleep   59    0   0:00:00 0.0% syseventd/14
    88 root     2520K  448K sleep   59    0   0:00:00 0.0% powerd/3
   650 root     8416K 2624K sleep   59    0   0:00:00 0.0% sshd/1
   180 root     2600K  192K sleep   59    0   0:00:00 0.0% cron/1
Total: 66 processes, 174 lwps, load averages: 1.00, 1.14, 1.27


Is this normal? It seems a lot to build some documents to me. The
process is basically CPU bound, using 50% of the CPU on this dual
processor machine. (2 x 900 MHz UltraSPARC III+ CPUs).

The two columns of interest are defined as

    SIZE

         The total virtual memory size of the process,  including
         all  mapped  files  and devices, in kilobytes (K), mega-
         bytes (M), or gigabytes (G).

     RSS

         The resident set size of the process (RSS), in kilobytes
         (K),  megabytes  (M), or gigabytes (G). The RSS value is
         an estimate provided by proc(4) that might underestimate
         the actual resident set size. Users who want to get more
         accurate usage information for capacity planning  should
         use the -x option to pmap(1) instead.

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Reply via email to