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


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 Beshers



Hans Reiser wrote:

> Alex Zarochentsev wrote:
>
>> On Tue, Jun 22, 2004 at 07:29:33PM -0700, Hans Reiser wrote:
>>  
>>
>>> http://www.namesys.com/intbenchmarks/mongo/04.05.04/256MB.RAM/comparison/smart-8k.noENTD.vs.ENTD/comp-ENTD.vs.noENTD.html 
>>>
>>>   
>>
>>
>> Because direct page reclaiming (when a thread which needs memory does 
>> try_to_relase_page() by itself) is better then indirect one (through
>> ENTD or whatever page reclaiming daemon).  It is why Linux uses direct
>> page reclaiming not indirect.
>>
>>  
>>
> I apologize to zam, I meant to only cc this to reiserfs-dev.
> I think this performance loss can be overcome, and needs to be 
> overcome so we can eliminate emergency flush and get good iozone 
> results.  I should note though that Andrew Morton thinks iozone is a 
> benchmark that does things that no application does (dirtying massive 
> amounts of mmap'd pages).  I am curious as to whether the sysadmins on 
> the list would agree with that (Andrew may be right)....
>


  reply	other threads:[~2004-06-23 18:03 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     ` George Beshers [this message]
2004-06-24  5:13       ` iozone reality check: was " Hans Reiser
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=40D9C5F5.7010605@comcast.net \
    --to=gbeshers@comcast.net \
    --cc=reiser@namesys.com \
    --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.