Re: [Caml-list] concurrent gc?

[Malcolm Matalka <mmatalka@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1615 bytes --]

It's highly dependent on the situation but in my experience the goal is
almost always to avoid doing a collection over all 60 gb.  It's expensive
no matter how you do it.  Solutions include spreading the data over
multiple processes and/or moving the data outside the managed heap.
Ocaml-ancient is worth looking at as well.
Den 24 jul 2014 09:01 skrev "Nicolas Boulay" <nicolas@boulay.name>:

> 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 <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.
>>
>>  > 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
>>
>
>

[-- Attachment #2: Type: text/html, Size: 2506 bytes --]