From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id EE0667FA4D for ; Tue, 29 Jul 2014 19:23:44 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of raould@gmail.com) identity=pra; client-ip=209.85.218.43; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="raould@gmail.com"; x-sender="raould@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of raould@gmail.com designates 209.85.218.43 as permitted sender) identity=mailfrom; client-ip=209.85.218.43; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="raould@gmail.com"; x-sender="raould@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-oi0-f43.google.com) identity=helo; client-ip=209.85.218.43; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="raould@gmail.com"; x-sender="postmaster@mail-oi0-f43.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArcBAErY11PRVdorm2dsb2JhbABZhDcEgnTQRAGBBwgWEAEBAQEBBgsLCRQphAQBAQMBEhEdARseAwELBgULDwImAgIiAREBBQEcBjWICwEDCQibTWqLKYFygxCKaAoZJw1khiURAQUOgR6OJ4J5gVEFinKQXZJcGCmFGh0v X-IPAS-Result: ArcBAErY11PRVdorm2dsb2JhbABZhDcEgnTQRAGBBwgWEAEBAQEBBgsLCRQphAQBAQMBEhEdARseAwELBgULDwImAgIiAREBBQEcBjWICwEDCQibTWqLKYFygxCKaAoZJw1khiURAQUOgR6OJ4J5gVEFinKQXZJcGCmFGh0v X-IronPort-AV: E=Sophos;i="5.01,758,1400018400"; d="scan'208";a="87487046" Received: from mail-oi0-f43.google.com ([209.85.218.43]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 29 Jul 2014 19:23:43 +0200 Received: by mail-oi0-f43.google.com with SMTP id u20so7665702oif.30 for ; Tue, 29 Jul 2014 10:23:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=2NUp1OUW7OBke/UHm6SUCIo92cvX+VzuQrINeHav4Es=; b=TS1hw0deTMApxjX0pufWbrlwbDXFIIc2Ifk7pEK0U/3lquXPQN0E1kcASI7oRh7uQR 7IBxP0XsHD3dgidW48ZoqHpfMUZ378fkjXBVORSUgcjMvzLvSB8ruGXkSy2KH7UrrgiR gxEGRIwOGgpBSwMbzPmYULNjIEYrj5MfLmj212DQKaF/2L+25n+O9tthbizZ1jxdyC2J QtJqH7zJxNcjAiRLusRdzSen0vzqyBggo+KOuutCDi3XeBh7I55sYSH/FVzjn7wuvmkI gTTZwio9MIf9hRLrjHw7egYgpF5i6FqcCmv9BPteDEtd9uYtZKSBDTXX775TL9grDNiQ yqbw== X-Received: by 10.182.27.5 with SMTP id p5mr5622732obg.42.1406654622314; Tue, 29 Jul 2014 10:23:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.151.101 with HTTP; Tue, 29 Jul 2014 10:23:22 -0700 (PDT) In-Reply-To: References: <21456.19915.45180.915211@gargle.gargle.HOWL> <20140728112431.GC26816@frosties> From: Raoul Duke Date: Tue, 29 Jul 2014 10:23:22 -0700 Message-ID: To: OCaml Content-Type: text/plain; charset=UTF-8 Subject: Re: [Caml-list] concurrent gc? > 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. :-)