All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: George Beshers <gbeshers@comcast.net>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: iozone reality check: was zam, please discuss this
Date: Wed, 23 Jun 2004 22:13:04 -0700	[thread overview]
Message-ID: <40DA62E0.2050803@namesys.com> (raw)
In-Reply-To: <40D9C5F5.7010605@comcast.net>

George Beshers wrote:

>
> Caveat: I have not looked at the iozone test so this is purely in 
> response
> to Han's description.
>
> The examples I know of are apps that allocate an mmap'd area for garbage
> collection: ocaml, sml-nj, and I believe ghc (Haskell) do this.  While 
> these
> systems usually have generational GCs at some point major collections
> happen and then I *believe* that you will see lots of dirty pages.
>
> Note: the 'believe' is based on some experiments on an SGI ccNuma
> system with profiling tools---I was looking at local access issues and
> noticed the pattern of changes to flag objects as "marked" in a 
> mark/sweep
> collector.  I then tried ocaml as an experiment and saw something
> similar.
>
>
> I have not look at Boehm conservative collector in some time, but if
> memory serves me correctly it uses separate arrays to hold the bits;
> using mmap is an option---I don't know if it is in common use.
>
> Some 18-20 months ago I spent some time looking at the Java GC
> but I don't remember its using mmap() and I no longer have the source
> available.
>
> George Besher

When you say lots, do you mean close to or more than physical ram?

  reply	other threads:[~2004-06-24  5:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23  2:29 zam, please discuss this Hans Reiser
2004-06-23  6:30 ` Alex Zarochentsev
2004-06-24  3:33   ` Hans Reiser
2004-06-24  4:29   ` Hans Reiser
2004-06-23 18:03     ` iozone reality check: was " George Beshers
2004-06-24  5:13       ` Hans Reiser [this message]
2004-06-23 18:36         ` George Beshers
2004-06-24  7:11           ` Hans Reiser

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=40DA62E0.2050803@namesys.com \
    --to=reiser@namesys.com \
    --cc=gbeshers@comcast.net \
    --cc=reiserfs-list@namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.