caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: SerP <serp256@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Memory fragmentation
Date: Fri, 20 Apr 2012 22:32:50 +0400	[thread overview]
Message-ID: <CAHgca+_BGYZC=tvNqMBS+iEhw-vbnPzO3s8qhRxbsxJm_pzxTw@mail.gmail.com> (raw)
In-Reply-To: <4F9191D5.6060809@etorok.net>

[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]

>
> If that is the case then maybe it would help to try and allocate memory in
> the OCaml's runtime by using mmap() directly.
>
Yes, i need to try this.

>
> Is your application completely single-threaded (since you're using lwt),
> or do you also use multiple threads?
> I think that glibc caches mmap-ed areas even if you free them (i.e.
> they're still mapped into your process but they might be changed via
> mprotect() to PROT_NONE), which is especially a problem if you use multiple
> threads.
>
Lwt use threads for some bloking system calls, so my application has
multiple threads.

Strange behaviour is that the before (first|second) compaction all ocaml
memory (1GB) was in mmaped area, but after all ocaml memory in placed in
brked memory and later all allocations occurs throught brk. major_heap - is
2MB


> Best regards,
> --Edwin
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>

[-- Attachment #2: Type: text/html, Size: 1838 bytes --]

  reply	other threads:[~2012-04-20 18:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHgca+9-K71NynNVzS0Stnb2v5Tc6n5ecCnJHZorhuB8y8EdTw@mail.gmail.com>
2012-04-20 15:12 ` SerP
2012-04-20 15:27   ` [Caml-list] " SerP
2012-04-20 16:41   ` [Caml-list] " Török Edwin
2012-04-20 18:32     ` SerP [this message]
2012-04-20 21:32   ` ygrek
2012-04-21  7:26   ` rixed
2012-04-24 19:24     ` SerP

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='CAHgca+_BGYZC=tvNqMBS+iEhw-vbnPzO3s8qhRxbsxJm_pzxTw@mail.gmail.com' \
    --to=serp256@gmail.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).