From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@inria.fr
Subject: Performance-question
Date: Tue, 5 Feb 2008 14:33:53 +0100 [thread overview]
Message-ID: <1202218433.47a865c1d3619@webmail.in-berlin.de> (raw)
Hello,
I have a concrete (non philosophical) question
on the Performance of one of my scripts.
The general behaviour: it reads data fast first,
then slows down a lot (possibly after about 1/3 of the
data; it seems to completely have stopped then), then later speeds up
again.
Ths script needs nearly complete CPU-time and the system load goes up.
Now here some data:
=====================================================
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
----------------------------------------------------------------------
minor_words: 218494242
promoted_words: 38303811
major_words: 3546606791
minor_collections: 64811
major_collections: 720
heap_words: 1044480
heap_chunks: 17
top_heap_words: 47322112
live_words: 666290
live_blocks: 103159
free_words: 378186
free_blocks: 360
largest_free: 60034
fragments: 4
compactions: 131
=====================================================
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?
Ciao,
Oliver
next reply other threads:[~2008-02-05 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 13:33 Oliver Bandel [this message]
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
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=1202218433.47a865c1d3619@webmail.in-berlin.de \
--to=oliver@first.in-berlin.de \
--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