caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: John Lepikhin <john@ispsystem.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] memory usage
Date: Mon, 12 Jan 2009 23:05:20 +0800	[thread overview]
Message-ID: <1231772720.4376.217.camel@john-laptop> (raw)
In-Reply-To: <20090112114837.GB18405@janestcapital.com>


> > Please, give me some start point to find the roots of the problem.
> I assume you're running on Linux.

I've got this issue on FreeBSD box. On Linux test box process grows only
up to 2MB (but there is no production data and clients). Here is partial
pmap output:

Address              Kbytes        RSS     Shared       Priv Mode
Mapped File
...
00000000408AA000        932        548        932          -
r-x   /lib/libc.so.7
0000000040993000          4          4          4          -
r-x   /lib/libc.so.7
0000000040994000       1020          0       1020          -
r-x   /lib/libc.so.7
0000000040A93000        116        116          -        116
rw-   /lib/libc.so.7
0000000040AB0000         92         44          -         92 rw-
[ anon ]
0000000040B00000       1024        904          -       1024 rw-
[ anon ]
0000000040C00000      34816      19652          -      34816 rw-
[ anon ]
0000000042E00000       1024        200          -       1024 rw-
[ anon ]
0000000042F00000       2048        400          -       2048 rw-
[ anon ]
00007FFFFB9BE000        128         20          -        128 rw-
[ anon ]
00007FFFFBBBF000        128         20          -        128 rw-
[ anon ]
...
---------------- ---------- ---------- ---------- ----------
Total Kb              48552      23736       4352      44528

Most of memory is allocated here:

0000000040C00000      34816      19652          -      34816 rw-
[ anon ]

It gets bigger and bigger:

0000000040C00000      34816      20660          -      34816 rw-
[ anon ]

0000000040C00000      34816      21216          -      34816 rw-
[ anon ]

> One other thing to check is to ensure that threads really are being killed
> at the times you expect.  (Check "/proc/<pid>/status | grep Threads", or use
> "gdb -p" to attach to the running process then "info thr".)

I checked it. Only valid threads run.


  parent reply	other threads:[~2009-01-12 15:05 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12  7:41 John Lepikhin
2009-01-12  8:39 ` [Caml-list] " Richard Jones
2009-01-12  9:14   ` John Lepikhin
2009-01-12 10:45     ` Sylvain Le Gall
2009-01-12 11:28       ` [Caml-list] " John Lepikhin
2009-01-12 11:41         ` Richard Jones
2009-01-12 15:03           ` John Lepikhin
2009-01-12 19:55             ` Richard Jones
2009-01-12 17:56           ` John Lepikhin
2009-01-12 20:12             ` Richard Jones
2009-01-12 21:34               ` John Lepikhin
2009-01-12 22:01                 ` Richard Jones
2009-01-13 16:00                   ` John Lepikhin
     [not found] ` <20090112114837.GB18405@janestcapital.com>
2009-01-12 15:05   ` John Lepikhin [this message]
2009-01-12 16:29 ` [Caml-list] " Florian Hars
2009-01-12 16:44   ` John Lepikhin
2009-01-12 17:55     ` Sylvain Le Gall
2009-01-12 18:01       ` [Caml-list] " John Lepikhin
2009-01-12 18:26         ` Sylvain Le Gall
  -- strict thread matches above, loose matches on Subject: below --
2017-01-30 16:39 [Caml-list] Memory Usage Umair Siddique
2017-01-30 16:42 ` Van Chan Ngo
2017-01-30 16:50   ` Evgeny Roubinchtein
2017-01-31 18:09     ` Umair Siddique
2017-02-01  9:04 ` Alain Frisch
2008-07-11 19:49 memory usage Jean Krivine
2008-07-11 21:49 ` [Caml-list] " Till Varoquaux
2008-07-11 22:01 ` Richard Jones
2008-07-15 17:06   ` Jean Krivine
2008-07-15 19:31     ` Andres Varon
2008-07-15 19:38       ` Jean Krivine
2008-07-16 14:16         ` Andres Varon
2008-07-16 16:27           ` Jean Krivine
2008-07-16 18:07             ` Jean Krivine
2008-07-16 18:44               ` Andres Varon
2008-07-16 18:54                 ` Jean Krivine

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=1231772720.4376.217.camel@john-laptop \
    --to=john@ispsystem.com \
    --cc=caml-list@yquem.inria.fr \
    /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).