caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: John Lepikhin <john@ispsystem.com>
To: caml-list@inria.fr
Subject: [Caml-list] Re: memory usage
Date: Mon, 12 Jan 2009 19:28:15 +0800	[thread overview]
Message-ID: <1231759695.4376.55.camel@john-laptop> (raw)
In-Reply-To: <slrngmm7qe.pbu.sylvain@gallu.homelinux.org>

> To get real memory used, (Sys.word_size * live_word / 8). Do you use
> out-of-heap datastructure that can use memory ? (malloc-ed
> datastructure).

The only specific module is ocaml-fd (send file descriptors over pipes).
I have suspicion on it, but as I said before, 90% of process memory is
filled with specific text data, which is got inside threads and sent to
socket using Unix.write. This data doesn't look like file
descriptors :-)
All other modules are from distribution (Unix, String, Mutex, Threads).

I heard about ocaml-memprof patch. Will it help here?


  reply	other threads:[~2009-01-12 11:28 UTC|newest]

Thread overview: 19+ 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       ` John Lepikhin [this message]
2009-01-12 11:41         ` [Caml-list] " 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   ` [Caml-list] " John Lepikhin
2009-01-12 16:29 ` 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

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=1231759695.4376.55.camel@john-laptop \
    --to=john@ispsystem.com \
    --cc=caml-list@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).