From: "François Bobot" <francois.bobot@cea.fr>
To: Alain Frisch <alain.frisch@lexifi.com>, caml-list@inria.fr
Subject: Re: [Caml-list] Presumed bug in OCaml's garbage collector or in its Weak module...
Date: Wed, 22 Jun 2016 10:12:10 +0200 [thread overview]
Message-ID: <f21ab7a0-e592-f8dd-8459-9acaf9e04580@cea.fr> (raw)
In-Reply-To: <8718df5d-2129-2404-ab56-188331d15a6d@lexifi.com>
On 21/06/2016 21:37, Alain Frisch wrote:
>
> Not directly related to this thread, but it might be worth mentioning
> that for our use case (hash-consing terms), disabling the shallow copy
> (i.e. using get instead of get_copy) lead to very significant
> performance gains.
It's an interesting report. The contrary of Doligez and Cuoq paper[1], but the usage of hashconsing
in Frama-C is quite different from yours.
>
> Perhaps the "official" Weak.Make should at least allow to use get
> instead of get_copy?
Before complicating the API, I would prefer to check what happend if we get ride of get_copy but
keep the nice property (by complicating the runtime...). In your case forcing the keeping of some
value explicitly with a usual "hard" cache (with LRU stategy?) on top of the weak set could be
sufficient and more intelligible.
[1]: http://cristal.inria.fr/~doligez/publications/cuoq-doligez-mlw-2008.pdf
--
François
next prev parent reply other threads:[~2016-06-22 8:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 18:09 "Martin R. Neuhäußer"
2016-06-17 19:23 ` Gabriel Scherer
2016-06-18 15:15 ` "Martin R. Neuhäußer"
2016-06-17 19:41 ` Török Edwin
2016-06-17 20:29 ` "Martin R. Neuhäußer"
2016-06-18 10:59 ` Josh Berdine
2016-06-18 15:11 ` "Martin R. Neuhäußer"
2016-06-18 16:54 ` Leo White
2016-06-21 12:43 ` François Bobot
2016-06-21 19:37 ` Alain Frisch
2016-06-22 8:12 ` François Bobot [this message]
2016-06-18 17:39 ` "Martin R. Neuhäußer"
2016-06-21 11:55 ` François Bobot
2016-06-27 11:35 ` AW: " Neuhaeusser, Martin
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=f21ab7a0-e592-f8dd-8459-9acaf9e04580@cea.fr \
--to=francois.bobot@cea.fr \
--cc=alain.frisch@lexifi.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).