XmlValidatingReader memory behaviour

[Paul Hatcher]

I need to validate a number of different XML documents against the same
schema, but the behaviour of XmlValidatingReader seems to make this very
expensive in memory terms.

We loaded about 150 XML files via XmlDocument.Load, which took around about
3Mb of allocations, but the XmlValidatingReader added another 69Mb of
allocations during Schema.Add

What would be nice is if you could create a validating reader and assign the
schema and then have it process multiple XML documents; currently the reader
has to be passed in via the constructor so you can't re-use the internal
schema set up that's expensive in memory terms.

Paul

[Priya Lakshminarayanan [MSFT]]

You can add all your schemas to an XmlSchemaCollection and then re-use this
schema collection with multiple XmlValidatingReaders that are created over
your multiple XML documents. This will ensure that the schemas are compiled
only once.

Thanks,
Priya

"Paul Hatcher" <ph******@spamless.cix.co.uk> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

I need to validate a number of different XML documents against the same
schema, but the behaviour of XmlValidatingReader seems to make this very
expensive in memory terms.

We loaded about 150 XML files via XmlDocument.Load, which took around about 3Mb of allocations, but the XmlValidatingReader added another 69Mb of
allocations during Schema.Add

What would be nice is if you could create a validating reader and assign the schema and then have it process multiple XML documents; currently the reader has to be passed in via the constructor so you can't re-use the internal
schema set up that's expensive in memory terms.

Paul

[Paul Hatcher]

Priya

Thanks a lot for that - saved me a lot of hassle

Regards

Paul

"Priya Lakshminarayanan [MSFT]" <pr****@online.microsoft.com> wrote in
message news:42********@news.microsoft.com...

You can add all your schemas to an XmlSchemaCollection and then re-use
this
schema collection with multiple XmlValidatingReaders that are created over
your multiple XML documents. This will ensure that the schemas are
compiled
only once.

Thanks,
Priya

"Paul Hatcher" <ph******@spamless.cix.co.uk> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

I need to validate a number of different XML documents against the same
schema, but the behaviour of XmlValidatingReader seems to make this very
expensive in memory terms.

We loaded about 150 XML files via XmlDocument.Load, which took around

about

3Mb of allocations, but the XmlValidatingReader added another 69Mb of
allocations during Schema.Add

What would be nice is if you could create a validating reader and assign

the

schema and then have it process multiple XML documents; currently the

reader

has to be passed in via the constructor so you can't re-use the internal
schema set up that's expensive in memory terms.

Paul