RE: tinytree behaviour with document function

The most likely explanation is that one stylesheet specifies
<xsl:strip-space elements="*"/> and the other does not. The strip-space
declaration applies both to the principal input document and to documents
loaded using the document() function.

Michael Kay
http://www.saxonica.com/
 

> -----Original Message-----
> From: saxon-help-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx 
> [mailto:saxon-help-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx] 
> On Behalf Of 
> Christian Nentwich
> Sent: 23 June 2005 16:10
> To: saxon-help-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> Subject: [saxon] tinytree behaviour with document function
> 
> Hi,
> 
> we've got a problem here with Saxon (6.3.. but also tried on 8.4) in
> terms of memory usage.  We have a file that is 140 meg on disk on disk
> and two stylesheets:
> 
>   * Style sheet A processes the file as input, and loads 3 files using
> document()
>   * Style sheet B processes a small file and loads the big 
> file using document()
> 
> The behaviour of Saxon in both cases is different. Style sheet A uses
> about 300 meg of memory (good performance!) but style sheet B uses
> over 900. Here is some trace output:
> 
> Building tree for 
> file:/export/home/nentwich/saxon_test/magix-instrument.xml usi
> ng class net.sf.saxon.tinytree.TinyBuilder                    
>                   
> Tree built in 154548 milliseconds                             
>                   
> Tree size: 2996345 nodes, 7816417 characters, 32097 
> attributes                  
> 
> Building tree for 
> file:/export/home/nentwich/saxon_test/magix-instrument.xml usi
> ng class net.sf.saxon.tinytree.TinyBuilder                    
>                   
> Tree built in 123578 milliseconds                             
>                   
> Tree size: 5787574 nodes, 77191047 characters, 32097 
> attributes                 
> 
> As you can see, when it is loaded using the document function it is a
> lot bigger. My analysis seems to indicate that this is due to Saxon
> setting up the tree builder differently (not eliminating whitespace).
> 
> Is this correct? And if yes, why does it not eliminate white space?
> Our file sizes are about to jump and this would make it impossible to
> use XSLT for this transformation in the future. Can we simply turn on
> white space stripping for included docs?
> 
> thanks,
> Christian
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=ick
> _______________________________________________
> saxon-help mailing list
> saxon-help-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/saxon-help
> 




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click