caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Chris Hecker <checker@d6.com>
To: Daniel Phillips <dan@dgph.net>, caml-list@inria.fr
Subject: Re: [Caml-list] Ocaml and games
Date: Fri, 25 Jan 2002 14:16:25 -0800	[thread overview]
Message-ID: <4.3.2.7.2.20020125141112.030791f0@arda.pair.com> (raw)
In-Reply-To: <20020126060133.365C.DAN@dgph.net>


>> The GC performance predicability and smoothness is a huge looming shadow on the horizon that may or may not materialize, I have no idea.
>Do you have any specific thoughts on this that you can share yet? Have you done any tests?

Nope.  It's just that the "conventional wisdom" is that GC will hurt performance, so I'm worried just on principle. :)  I haven't seen any indication that it will yet, however.

As the other poster said, doing full collections between levels seems like a reasonable thing to try.

I'm also slightly worried about the "write barrier" thing, which I've seen posted about but don't fully understand yet.  To avoid GC activity I may want to keep some arrays around and reuse them, but apparently as they migrate into the old heap then you get the write barrier thing going on.  Hopefully this won't be a problem either, but I don't know yet (I don't know if I understand it correctly yet, either).

Lots of fun adventures on the horizon, I'm sure...just hopefully no show-stoppers. ;)

Chris


-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  parent reply	other threads:[~2002-01-25 22:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-21 23:27 cgillot
2002-01-21 22:43 ` [Caml-list] Re: your mail Markus Mottl
2002-01-22  0:03   ` [Caml-list] Re: about toplevels cgillot
2002-01-22 20:41     ` Chris Hecker
2002-01-22 21:35       ` [Caml-list] Ocaml and games Matthew D Moss
2002-01-22 21:43         ` Will Benton
2002-01-22 23:53         ` Eric C. Cooper
2002-01-23  0:58         ` Ian Zimmerman
2002-01-23  1:23         ` Yaron M. Minsky
2002-01-23  3:29         ` Doug Bagley
2002-01-23  5:20         ` Chris Hecker
2002-01-24  3:02           ` Matthew D Moss
2002-01-24  6:59           ` Chris Hecker
2002-01-25 20:22           ` Daniel Phillips
2002-01-25 20:53             ` Ken Rose
2002-01-25 22:16             ` Chris Hecker [this message]
2002-01-25 23:00               ` Thatcher Ulrich
2002-01-23  8:39         ` Sven
2002-01-23 15:35         ` Xavier Leroy
2002-01-22  9:00   ` [Caml-list] Re: your mail Daniel de Rauglaudre
2002-01-22 13:12     ` Markus Mottl
     [not found] ` <4.3.2.7.2.20020123011902.00cde840@arda.pair.com>
2002-01-23  9:35   ` [Caml-list] Re: about toplevels Christian Gillot
2002-01-23 10:20     ` Chris Hecker
2002-01-24 16:03     ` Daniel de Rauglaudre
2002-01-24 17:20       ` Christophe Raffalli
2002-01-24 17:34       ` Christian Gillot
2002-01-24 20:42     ` [Caml-list] gotchas [Was: toplevels] Ian Zimmerman
2002-01-25 10:59       ` Christian Gillot
2002-01-25 11:17         ` Sven

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=4.3.2.7.2.20020125141112.030791f0@arda.pair.com \
    --to=checker@d6.com \
    --cc=caml-list@inria.fr \
    --cc=dan@dgph.net \
    /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).