Re: Xalan 2.2 Memory Usage

2001-11-16 Thread Chris McCabe
Is there a simple way to turn off the cacheing at the API level for testing purposes so I can see if the memory problems go away?  At least I would know if that was the problem or not and could go from there. Chris [EMAIL PROTECTED] wrote: [EMAIL PROTECTED]"> On Friday, 11/16/2001 at 10:11 C

Re: Xalan 2.2 Memory Usage

2001-11-16 Thread Joseph_Kesselman
On Friday, 11/16/2001 at 10:11 CET, Claudio Sacerdoti Coen <[EMAIL PROTECTED]> wrote: > be possible to have the PI extended also to the case of > document() in head position inside the select of a xsl:copy-of? We know we need a general answer to the question of DTM cache control -- preferably

Re: Xalan 2.2 Memory Usage

2001-11-16 Thread Joseph_Kesselman
On Thursday, 11/15/2001 at 04:52 MST, "Chris McCabe" <[EMAIL PROTECTED]> wrote: > If we load the > same documents over and over, would we see increasing memory > consumption, or does it reuse the cached version? It's supposed to reuse. But if you're having memory use problems, we should check th

Re: Xalan 2.2 Memory Usage

2001-11-16 Thread Claudio Sacerdoti Coen
> If you're using document() heavily, there are some known issues regarding > whether/when/how-long a DTM is retained in memory. There's a PI that can be > used as a workaround in the common case of an with a > document()-based expression in its select, but a general and automated > answer is sti

Re: Xalan 2.2 Memory Usage

2001-11-15 Thread Chris McCabe
We do use document() from 1-3 times with every transformation, but there are only a handful of unique documents that get loaded. The total of all documents loaded is less than 1 Meg of text XML. If we load the same documents over and over, would we see increasing memory consumption, or does

Re: Xalan 2.2 Memory Usage

2001-11-15 Thread Joseph_Kesselman
If you're using document() heavily, there are some known issues regarding whether/when/how-long a DTM is retained in memory. There's a PI that can be used as a workaround in the common case of an with a document()-based expression in its select, but a general and automated answer is still being

Xalan 2.2 Memory Usage

2001-11-15 Thread Chris McCabe
Does anyone have any data on memory usage for Xalan 2.2 compared to 2.1? We have found that 2.2 is consuming a great deal more memory than 2.1, to a point that it brings our server to its knees. Xalan 2.1 runs fine and under a moderate load we are consuming a total of around 150-200 Meg of me