From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Performance-question
Date: Tue, 5 Feb 2008 13:51:03 +0000 [thread overview]
Message-ID: <200802051351.04092.jon@ffconsultancy.com> (raw)
In-Reply-To: <1202218433.47a865c1d3619@webmail.in-berlin.de>
On Tuesday 05 February 2008 13:33:53 Oliver Bandel wrote:
> For me it looks like a lot of GC-actions, but I'm not sure in that
> point. What do you think is slowing down here, and how to avoid
> this behaviour?
You need to run a memory profiler on your code to work out where it is
allocating all of that data.
I've had the same problem and wrote my own memory profiler. I may
commercialize it in the future...
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/products/?e
next prev parent reply other threads:[~2008-02-05 14: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 ` Jon Harrop [this message]
2008-02-05 16:18 ` [Caml-list] Performance-question Oliver Bandel
2008-02-07 16:13 ` Damien Doligez
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=200802051351.04092.jon@ffconsultancy.com \
--to=jon@ffconsultancy.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).