From: Raoul Duke <raould@gmail.com>
To: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] concurrent gc?
Date: Tue, 29 Jul 2014 10:23:22 -0700 [thread overview]
Message-ID: <CAJ7XQb5yXavK=qF4B3Uqd4ot-_O5ww=b+o4gYStWK7kOcSJX+w@mail.gmail.com> (raw)
In-Reply-To: <CAPFanBFw9PUua4GmU+RwwGczmtykA9Qvk1Knv8xdb_aUPGpLKA@mail.gmail.com>
> Do you have practical experience with OCaml programs with unacceptable
> pauses, or is this discussion just premature GC optimization? Having a
> concrete example to work with could be interesting.
this is premature gc optimization.
there was a time when i would have had real data, but there were FFI
bugs (as far as i could tell) with ocaml and one of the labltk or
whatever opengl libraries and it wasn't ever something resolved so i
gave up and moved on to other ecosystems.
so were i to get back into ocaml it would be with some trepidation
since i've been fairly burned a bit before with it. of course, mostly
all systems will burn me one way or another. with haxe + hxcpp on
android, the gc seems to be what is killing me, at least on the
low-end devices which i assume have smaller cpu caches. something.
so i've been looking at other things again. ocaml has a lot going for
it on paper, i've always been a fan of it, i try to attend local ocaml
meetups, etc. so i'm not a complete hater. but i really do not want
there to be any gc pauses or as few as possible so it is fun to learn
if i have any way to influence that, and how hard that can be to
achieve. e.g. with haxe+hxpp on android i think i'd have to really
dive into the sources and get the android nkd profiling working etc.
etc. etc. which feels like way too much work.
:-)
next prev parent reply other threads:[~2014-07-29 17:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 23:34 Raoul Duke
2014-07-24 0:05 ` John F. Carr
2014-07-24 0:08 ` Raoul Duke
2014-07-24 0:44 ` John F. Carr
2014-07-24 0:45 ` Raoul Duke
2014-07-24 15:24 ` Shayne Fletcher
2014-07-24 3:45 ` Malcolm Matalka
2014-07-24 5:58 ` Anthony Tavener
2014-07-28 11:20 ` Goswin von Brederlow
2014-07-24 6:58 ` Nicolas Boulay
2014-07-24 7:38 ` Malcolm Matalka
2014-07-24 15:36 ` Fabrice Le Fessant
2014-07-24 15:39 ` Malcolm Matalka
2014-07-24 16:44 ` Fabrice Le Fessant
2014-07-25 7:18 ` Nicolas Boulay
2014-07-28 11:26 ` Goswin von Brederlow
2014-07-28 11:24 ` Goswin von Brederlow
2014-07-28 17:34 ` Raoul Duke
2014-07-29 4:25 ` Gabriel Scherer
2014-07-29 4:49 ` ygrek
2014-07-29 10:01 ` Goswin von Brederlow
2014-07-29 10:29 ` ygrek
2014-07-31 11:10 ` Goswin von Brederlow
2014-07-29 17:23 ` Raoul Duke [this message]
2014-12-19 0:58 ` Jon Harrop
2014-07-31 14:26 ` Richard W.M. Jones
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='CAJ7XQb5yXavK=qF4B3Uqd4ot-_O5ww=b+o4gYStWK7kOcSJX+w@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