From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Performance-question
Date: Tue, 5 Feb 2008 17:18:52 +0100 [thread overview]
Message-ID: <1202228332.47a88c6c1c3cf@webmail.in-berlin.de> (raw)
In-Reply-To: <200802051351.04092.jon@ffconsultancy.com>
Zitat von Jon Harrop <jon@ffconsultancy.com>:
> 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.
[...]
Oh, I hope I can solve that problem otherwise.
I have some suspicious functions...
...possibly I should now switch to better datastructures/algorithms.
I hope I can solve it this way.
But thanks for your hint.
Ciao,
Oliver
next prev parent reply other threads:[~2008-02-05 16:18 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 [this message]
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=1202228332.47a88c6c1c3cf@webmail.in-berlin.de \
--to=oliver@first.in-berlin.de \
--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).