caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Damien Doligez <damien.doligez@inria.fr>
To: caml users <caml-list@inria.fr>
Cc: Oliver Bandel <oliver@first.in-berlin.de>
Subject: Re: [Caml-list] Performance-question
Date: Thu, 7 Feb 2008 17:13:25 +0100	[thread overview]
Message-ID: <CE49CA70-EEE5-4B54-9595-FB41B69E8BFF@inria.fr> (raw)
In-Reply-To: <1202218433.47a865c1d3619@webmail.in-berlin.de>


On 2008-02-05, at 14:33, Oliver Bandel wrote:

> Each sample counts as 0.01 seconds.
>  %   cumulative   self              self     total
> time   seconds   seconds    calls   s/call   s/call  name
> 44.45    163.08   163.08    26627     0.01     0.01  mark_slice
> 22.31    244.92    81.84    38447     0.00     0.00  sweep_slice
> 14.40    297.74    52.82      131     0.40     0.61  caml_compact_heap
>  3.49    310.54    12.80 372416920     0.00     0.00   
> invert_pointer_at
>  3.40    323.02    12.48 560604006     0.00     0.00  compact_allocate
>  3.12    334.45    11.43  9725772     0.00     0.00  caml_fl_allocate
>  0.92    337.81     3.36    25607     0.00     0.00  caml_add_to_heap

That's a lot of time spent in the compactor, indicating that your
program has a memory fragmentation problem.

I would be very interested in getting a copy of your program and data,
as I'm currently experimenting with new allocation policies designed
to reduce fragmentation.  This would make a good benchmark for me.

More generally, I'm looking for (small) programs that exhibit this
kind of behaviour: they call the compactor frequently and their memory
usage grows without bound when the compactor is disabled.

-- Damien


  parent reply	other threads:[~2008-02-07 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 13:33 Performance-question Oliver Bandel
2008-02-05 13:51 ` [Caml-list] Performance-question Jon Harrop
2008-02-05 16:18   ` Oliver Bandel
2008-02-07 16:13 ` Damien Doligez [this message]
2008-02-07 16:23   ` Jon Harrop

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=CE49CA70-EEE5-4B54-9595-FB41B69E8BFF@inria.fr \
    --to=damien.doligez@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=oliver@first.in-berlin.de \
    /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).