caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Raoul Duke <raould@gmail.com>
To: caml-list <caml-list@inria.fr>
Subject: [Caml-list] meta-gc (Re: concurrent gc?)
Date: Thu, 24 Jul 2014 10:37:19 -0700	[thread overview]
Message-ID: <CAJ7XQb6KZrjqj=4hdMEkWZd=KT47xmwu=E-6x7wDjam3Vz6zPQ@mail.gmail.com> (raw)

> I agree with Malcolm's experience, and my situation might be similar to
> yours: games -- a lot of allocations at high framerate. I'm guessing this
> from how evil you consider pauses to be. ;)

yes, interactive apps.

> allocators -- you still need to use dynamic allocations wisely. Here, I
> think the biggest problem is when you have a GC, you lose awareness of the
> allocations you're triggering.

yes, those are nice down to earth wise words that need to be said more
often in every class :-)

to kick the question up a meta-level: Does anybody have thoughts on
how to best orthogonalize actual memory allocation from where the
application says it wants it? I mean if I write a stupid loop that
makes a zillion particles in the middle of each frame render then yes
I'm an idiot, sure... but what things can be done to actually allow
such idiocy to squeak by?

Maybe that's a horrible thing to suggest as it just panders. But I
like to think of it more along the lines of trying to tease things
apart as much as possible, and then some more (to corrupt an infamous
meme).

[In some sense that is what GC purported to be when it was being sold
like snake oil :-) and for a long time "regular" programmers knew
better and would make fun of e.g. lisp programmers.]

             reply	other threads:[~2014-07-24 17:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 17:37 Raoul Duke [this message]
2014-07-24 19:34 ` John F. Carr
2014-07-24 19:46   ` Raoul Duke
2014-07-25  7:28 ` Nicolas Boulay

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='CAJ7XQb6KZrjqj=4hdMEkWZd=KT47xmwu=E-6x7wDjam3Vz6zPQ@mail.gmail.com' \
    --to=raould@gmail.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).