9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] leaks?
Date: Thu,  5 Jun 2003 20:35:02 +0200	[thread overview]
Message-ID: <a8119181176c3910a1acfa12c0f5bfb8@plan9.escet.urjc.es> (raw)

I've been monitoring the memory usage in our file server and it seems
to steadily increase.  This script shows the growing memory usage from
our last reboot (but it seems to keep on growing according to the
records for other periods of (up)time).

The numbers have been collected by cron at 3am, when there's almost no
system activity.

#!/bin/rc
# w swapstats
cat $0 | grep '^[0-9]' | awk -F/ '{print $1}' | graph -a | plot
exit ''
53150/110163 memory 0/160000 swap
53350/110163 memory 0/160000 swap
53857/110163 memory 0/160000 swap
54082/110163 memory 0/160000 swap
54583/110163 memory 0/160000 swap

A ps reveals that it might be both venti and fossil the ones eating memory.

For example, these are fossil and venti initially:
elf              34    0:00   0:00   11872K Rendez   venti
elf              41    0:00   0:00  190132K Rendez   fossil [cons]


these are the numbers after four days:
elf              34    0:00   0:00   12384K Rendez   venti
elf              41    0:00   0:00  190480K Rendez   fossil [cons]


Does this happen at other sites?
It's not a big deal, but might be of concern if we want to leave the
machine unattended for a long period of time.
I didnt try leak w/ them (anyone did?)

thanks a lot

PS: BTW, both venti and fossil work just great and rock solid here. We had
no problem at all.



             reply	other threads:[~2003-06-05 18:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05 18:35 Fco.J.Ballesteros [this message]
2003-06-06 15:26 ` rog
2003-06-06 15:30   ` Fco.J.Ballesteros

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a8119181176c3910a1acfa12c0f5bfb8@plan9.escet.urjc.es \
    --to=nemo@plan9.escet.urjc.es \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).