Google Groups Home
Help | Sign in
Message from discussion Concurrent GC: a good thing?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
Vityok  
View profile
 More options Jun 12 2007, 2:52 am
Newsgroups: comp.lang.functional
From: Vityok <bob...@ua.fm>
Date: Mon, 11 Jun 2007 23:52:12 -0700
Local: Tues, Jun 12 2007 2:52 am
Subject: Re: Concurrent GC: a good thing?
Jon Harrop        :

> Daniel C. Wang wrote:
> > So long as the two threads don't share any common mutable state. I think
> > two separate processes with their own single-threaded GC will always be
> > more efficient than a concurrent GC running two threads. The general
> > case of GCing concurrent threads that share mutable state is
> > fundamentally more difficult than having two threads that share no state
> > with separate GCs.

> So concurrent GC makes communication cheaper at the expense of everything
> else?

It seems to me, that marshalling can be worked around by implementing
specific serializer/deserializer functions for data structures being
processed.

Thanks to the binary I/O API of the ExtLib[1], I was able to reduce
the size of data produced by marshalling records.  Though, I did not
benchmark performance.

[1]  http://ocaml-lib.sourceforge.net/doc/IO.html

With best regards,
Victor Anyakin


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2008 Google