Performance tests (and our experiences) were showing that enabling defer
node expansion degrades performance on small documents even if processing
only part of them. This was a few months back...have recent improvements
changed this situation as far as anyone knows?
Joseph Kesselman
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
om> cc:
Subject: Re: Defer node
expansion
11/20/2002 09:31
AM
Please respond to
xerces-j-user
On Wednesday, 11/20/2002 at 02:46 ZE2, Pavel Ausianik
<[EMAIL PROTECTED]> wrote:
> Could somebody explain when the defer node expansion should be used in
> xerces 2?
1) When you don't intend to examine the entire document, this choice can
save memory and parsing time.
2) When latency (time before you can access the first node) is more
important than throughput (time before you can access the last node), this
choice can make your program more responsive.
Hence, deferred node expansion tends to be particularly helpful when
processing only part of a large document. But it may cost performance when
processing all of a small document. That's why it's optional.
(Note the similarity to Xalan's "incremental DTM" mode.)
______________________________________
Joe Kesselman / IBM Research
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
