From: dmitry grebeniuk <gds-mlsts@moldavcable.com>
To: caml-list@inria.fr
Subject: approx. performance of memory operations
Date: Tue, 22 Nov 2005 12:01:46 +0200 [thread overview]
Message-ID: <397509111.20051122120146@moldavcable.com> (raw)
Hello.
I have a question about performance of memory operations.
Let's assume that I know everything about current memory allocations
and GC state: count of root values, total count and size of allocated
values, current size and free space in old and young heaps, settings
of GC and sizes of all memory objects in the questions below.
How much time and space (approximately, in O-notation) will consume
operations:
1) minor GC,
2) major GC,
3) allocation on young heap (if it really happens on young heap),
4) allocation on old heap,
5) assigning value X to mutable field of some value Y (in cases when:
(a. X and Y are both on young heap,
b. X and Y are both on old heap,
c. X is on young heap, Y is on old heap,
d. X is on old heap, Y is on young heap)
6) other operations that can consume time and space.
--
WBR,
dmitry mailto:gds-mlsts@moldavcable.com
reply other threads:[~2005-11-22 10:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=397509111.20051122120146@moldavcable.com \
--to=gds-mlsts@moldavcable.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).