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 E4A827FA56 for ; Thu, 24 Jul 2014 08:58:38 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of nicolas.boulay@gmail.com) identity=pra; client-ip=209.85.223.176; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="nicolas.boulay@gmail.com"; x-sender="nicolas.boulay@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of nicolas.boulay@gmail.com designates 209.85.223.176 as permitted sender) identity=mailfrom; client-ip=209.85.223.176; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="nicolas.boulay@gmail.com"; x-sender="nicolas.boulay@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-ie0-f176.google.com) identity=helo; client-ip=209.85.223.176; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="nicolas.boulay@gmail.com"; x-sender="postmaster@mail-ie0-f176.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiEEAA2u0FPRVd+wlGdsb2JhbABZg2BXBIJ0rxmVGIFhh0UmXAgWEAEBAQEHCwsJEiuEBAEBAwESER0BLQsBAwwBBQUEBxodAgIiEgEFAQoSGRIQiAwDCQgNnGFqiymFAop/JwMKhy4RAQUOjzmDAw+BPwWEcQWWPYFSkH8YKYFqgxA7Lw X-IPAS-Result: AiEEAA2u0FPRVd+wlGdsb2JhbABZg2BXBIJ0rxmVGIFhh0UmXAgWEAEBAQEHCwsJEiuEBAEBAwESER0BLQsBAwwBBQUEBxodAgIiEgEFAQoSGRIQiAwDCQgNnGFqiymFAop/JwMKhy4RAQUOjzmDAw+BPwWEcQWWPYFSkH8YKYFqgxA7Lw X-IronPort-AV: E=Sophos;i="5.01,722,1400018400"; d="scan'208";a="86757299" Received: from mail-ie0-f176.google.com ([209.85.223.176]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 24 Jul 2014 08:58:38 +0200 Received: by mail-ie0-f176.google.com with SMTP id tr6so1957800ieb.35 for ; Wed, 23 Jul 2014 23:58:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:cc:content-type; bh=pU0RJerCcYPQ0t7KkcR8BtU0ciRpBDTovbkUzRlhR5c=; b=OO2LzyKpdU8Sj6tNIVj4UickkvscgZotkbm5IoCf85bFp/FEhInJ596UCVw4vsHnqL UMtEseHSkKSYZ1KVKYPz4aFYPpDFXRQYZ7sPFZE1uih8p0IwG7WRn3xKZpNpXeYdLBfC 07WFWWhWK6sdO+hhxDjnYYKoYPUX7f/tCJe3IjDmaxmCMH92+PNM1tf7n+ghtbE/jHqr XI6hBrjUh7+H+51UVvhW5rbWeRka2qEfFU+t2TIKTXjv36uRytk8snFj0a60q8nB6GQ6 c4Wuxa0teuRFGHGUx1mg9qyKK8zPUcp2yaiCaQVEjB9T2hJTnNgOuJMj+sW1uT+yYlV9 POjA== MIME-Version: 1.0 X-Received: by 10.50.138.72 with SMTP id qo8mt5146395igb.2.1406185116860; Wed, 23 Jul 2014 23:58:36 -0700 (PDT) Sender: nicolas.boulay@gmail.com Received: by 10.50.73.131 with HTTP; Wed, 23 Jul 2014 23:58:36 -0700 (PDT) In-Reply-To: <21456.19915.45180.915211@gargle.gargle.HOWL> References: <21456.19915.45180.915211@gargle.gargle.HOWL> Date: Thu, 24 Jul 2014 08:58:36 +0200 X-Google-Sender-Auth: 6G7Yu3Z79c5cRaJADiW0fbyiTE8 Message-ID: From: Nicolas Boulay Cc: Raoul Duke , OCaml Content-Type: multipart/alternative; boundary=001a1134c7926120a004feeafc25 X-Validation-by: nicolas@boulay.name Subject: Re: [Caml-list] concurrent gc? --001a1134c7926120a004feeafc25 Content-Type: text/plain; charset=UTF-8 What about server that use ~60GB of RAM ? Todays server are sold with 32 to 256 GB of RAM and lot of cpu core. Maybe in such extreme cases, offloading the major collection of the GC could reduce latency a lot ? 2014-07-24 2:05 GMT+02:00 John F. Carr : > > Most programs spend a minority of their time in garbage collection. > Even if the new GC thread did not slow down the main program, > possible speedup would be less than 2x, probably well under 50%. > > For technical reasons, offloading major collections in OCaml is easier > than offloading minor collections, so the potential benefit is less. > > > extremely clueless question warning, both generally technically but > > also vis-a-vie ocaml specifically: > > > > so even if ocaml can't so easily be made to support multiple threads > > of ocaml code, could the gc be moved off to another thread? so that it > > could run on another core. would that be of any benefit? > > -- > Caml-list mailing list. Subscription management and archives: > https://sympa.inria.fr/sympa/arc/caml-list > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs > --001a1134c7926120a004feeafc25 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
What about server that use ~60GB of RAM ? Todays serv= er are sold with 32 to 256 GB of RAM and lot of cpu core.
Maybe i= n such extreme cases, offloading the major collection of the GC could reduc= e latency a lot ?


201= 4-07-24 2:05 GMT+02:00 John F. Carr <jfc@mit.edu>:

Most programs spend a minority of their time in garbage collection.
Even if the new GC thread did not slow down the main program,
possible speedup would be less than 2x, probably well under 50%.

For technical reasons, offloading major collections in OCaml is easier
than offloading minor collections, so the potential benefit is less.

=C2=A0> extremely clueless question warning, both generally technically = but
=C2=A0> also vis-a-vie ocaml specifically:
=C2=A0>
=C2=A0> so even if ocaml can't so easily be made to support multiple= threads
=C2=A0> of ocaml code, could the gc be moved off to another thread? so t= hat it
=C2=A0> could run on another core. would that be of any benefit?

--
Caml-list mailing list. =C2=A0Subscription management and archives:
ht= tps://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs

--001a1134c7926120a004feeafc25--