Re: Performance

Todd Byrne wrote:
> Björn Eickvonder wrote:
> 
>>So it's really xupdate..., unfortunately I couldn't find the sources for the
>>xupdate implementation or better a working cvs or subversion address. Do you
>>have any that works?
> 
> 
> I have also created a patch to eliminate the temporaryTree nodes that
> get left around. If we can convince Vadim to use a custom xupdate.jar I
> might invistage refactoring the library to remove that static variable.

I'd be in favor of custom xupdate jar as long as these conditions are met:

   (1) Patches are submitted to the official xupdate cvs repository
       but are sitting there without being committed;
   (2) Patched xupdate jar named as "xmldb-xupdate-YYYYMMDD-m.jar"
   (3) Diffs are checked in into xml-xindice SVN
   (4) README explaining what is this jar and why :-)

So that anybody can reproduce patched file knowing (2) and (3) after reading (4).

<snip/>

>>PS: By the way where and in what kind of form can/should I post XIndice
>>patches that I developed like a solution for the "too many open files
>>problem" that can occur on linux systems (if you have a large number of
>>collections)?

IMHO, you can create your collections with custom configuration which specifies 
maximum number of descriptors allowed (See CONFIG_DESCRIPTORS_MAX = 
"max-descriptors") instead of relying on the default (DEFAULT_DESCRIPTORS_MAX = 16).


> Just post them to [email protected] with PATCH in the title.
> Vadim will take a look at them when he has time.

Yup.

Vadim