From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
From: nemo@plan9.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: Re: [9fans] big pull
Date: Wed, 25 Jun 2003 09:48:22 +0200 [thread overview]
Message-ID: <bbc2d23fb7091a3c36f816195a8ae361@plan9.escet.urjc.es> (raw)
In-Reply-To: <cf560c0a18ae1880cfab7627ed087d8a@granite.cias.osakafu-u.ac.jp>
> By the way, the problem reported by Nemo before of fossil's
> memory leak has been fixed in the big pull? Or the problem
> was not recognized?
The incrase in memory size is not too much. When it runs enough days,
the increase in size is comparable to that of cs and some other programs.
Here are some numbers for a certain number of days.
I didnt trace where the memory went, though.
#!/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
54735/110163 memory 0/160000 swap
54701/110163 memory 0/160000 swap
54756/110163 memory 0/160000 swap
54810/110163 memory 0/160000 swap
54870/110163 memory 0/160000 swap
54791/110163 memory 0/160000 swap
54893/110163 memory 0/160000 swap
55006/110163 memory 0/160000 swap
55096/110163 memory 0/160000 swap
55095/110163 memory 0/160000 swap
55146/110163 memory 0/160000 swap
55304/110163 memory 0/160000 swap
55283/110163 memory 0/160000 swap
55368/110163 memory 0/160000 swap
55458/110163 memory 0/160000 swap
55504/110163 memory 0/160000 swap
55574/110163 memory 0/160000 swap
55609/110163 memory 0/160000 swap
next prev parent reply other threads:[~2003-06-25 7:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 10:35 Russ Cox
2003-06-23 10:49 ` Lucio De Re
2003-06-23 10:56 ` Lucio De Re
2003-06-24 2:20 ` Russ Cox
2003-06-23 14:02 ` Joel Salomon
2003-06-23 14:03 ` boyd, rounin
2003-06-23 14:20 ` Joel Salomon
2003-06-24 2:18 ` Russ Cox
2003-06-24 3:05 ` okamoto
2003-06-25 0:26 ` Russ Cox
2003-06-25 2:38 ` okamoto
2003-06-25 7:48 ` Fco.J.Ballesteros, nemo [this message]
2003-06-25 7:50 ` Lucio De Re
2003-06-25 8:01 ` Fco.J.Ballesteros, nemo
2003-06-25 7:56 ` Lucio De Re
2003-06-25 9:25 ` Richard Miller, miller
2003-06-26 1:57 ` Russ Cox
2003-06-26 9:11 ` Richard Miller, miller
2003-06-26 1:59 ` Russ Cox
2003-06-26 8:10 ` Fco.J.Ballesteros, nemo
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=bbc2d23fb7091a3c36f816195a8ae361@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).