XSL transform of a 30MB XML file

[gdumencu]

Hi,
When applied an XSL transform to a file bigger than 25 MB,
I've noticed big values for Mem. and VM :about 70,000K.
VM size didn't decrease even after 24 hours.
Calling the GC, Mem. usage and VM decreased immediately to
a reasonable size(<20,000K).

I'm wondering is there is a better way to manage XSL
transform of a big file.
Also I have no explanation why VM is still big if I'm not
calling GC from my program.

Thanks,
GD.

=============== =============== ==============
I tried several options but the result is similar.
1.
XPathDocument doc = new XPathDocument(X MLfile);
....
xslt.Transform( doc,null, stream,null);

2.
xslt.Transform( XMLfile, Rezfile, resolver);

[gdumencu]

Thank you.

I supposed that is the expected behavior of GC.

I'm still wondering if I should be concerned about
110,000KB VM size resulted after I applied an xml
transform to 29,000Kb XML file and than to a 20,000KB XML
file.
The value is a bit lower after a while but remains still
high in a 100,000 range even after 24 hours.

Regards,
GD

-----Original Message-----
Memory is typically not reclaimed (this applies not just to XSLT) untilthere is sufficient pressure on GC or by manually invoking the GC. If theallocated memory was needed by something else, the GC would haveautomaticall y reclaimed this memory. Since there was no added pressure, theGC did not invoke (and therefore saved some perf).
--
This posting is provided "AS IS" with no warranties, and confers no rights.Use of included script samples are subject to the terms specified athttp://www.microsoft.com/info/cpyright.htm.
"gdumencu" <gd******@hotma il.com> wrote in message
news:03******* *************** ******@phx.gbl. ..

Hi,
When applied an XSL transform to a file bigger than 25 MB, I've noticed big values for Mem. and VM :about 70,000K.
VM size didn't decrease even after 24 hours.
Calling the GC, Mem. usage and VM decreased immediately to a reasonable size(<20,000K).

I'm wondering is there is a better way to manage XSL
transform of a big file.
Also I have no explanation why VM is still big if I'm not calling GC from my program.

Thanks,
GD.

=============== =============== ==============
I tried several options but the result is similar.
1.
XPathDocument doc = new XPathDocument(X MLfile);
...
xslt.Transform( doc,null, stream,null);

2.
xslt.Transform( XMLfile, Rezfile, resolver);

.

[SQL Server Development Team [MSFT]]

Depending on the complexity of your stylesheet and XSLT, the working set
size can grow to be quite substantial as you've seen. This is an issue we
try to continually address, and will continue to do so in future versions of
System.Xml

Thanks,
Arpan Desai

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/copyright.htm.

"gdumencu" <gd******@hotma il.com> wrote in message
news:01******** *************** *****@phx.gbl.. .

Thank you.

I supposed that is the expected behavior of GC.

I'm still wondering if I should be concerned about
110,000KB VM size resulted after I applied an xml
transform to 29,000Kb XML file and than to a 20,000KB XML
file.
The value is a bit lower after a while but remains still
high in a 100,000 range even after 24 hours.

Regards,
GD

-----Original Message-----
Memory is typically not reclaimed (this applies not just

to XSLT) until

there is sufficient pressure on GC or by manually

invoking the GC. If the

allocated memory was needed by something else, the GC

would have

automaticall y reclaimed this memory. Since there was no

added pressure, the

GC did not invoke (and therefore saved some perf).
--
This posting is provided "AS IS" with no warranties, and

confers no rights.

Use of included script samples are subject to the terms

specified at

http://www.microsoft.com/info/cpyright.htm.
"gdumencu" <gd******@hotma il.com> wrote in message
news:03******* *************** ******@phx.gbl. ..

Hi,
When applied an XSL transform to a file bigger than 25 MB, I've noticed big values for Mem. and VM :about 70,000K.
VM size didn't decrease even after 24 hours.
Calling the GC, Mem. usage and VM decreased immediately to a reasonable size(<20,000K).

I'm wondering is there is a better way to manage XSL
transform of a big file.
Also I have no explanation why VM is still big if I'm not calling GC from my program.

Thanks,
GD.

=============== =============== ==============
I tried several options but the result is similar.
1.
XPathDocument doc = new XPathDocument(X MLfile);
...
xslt.Transform( doc,null, stream,null);

2.
xslt.Transform( XMLfile, Rezfile, resolver);

.