Re: XmlValidatingReader memory behaviour
- From: "Paul Hatcher" <phatcher@xxxxxxxxxxxxxxxxxx>
- Date: Sat, 2 Apr 2005 01:10:50 +0100
Priya
Thanks a lot for that - saved me a lot of hassle
Regards
Paul
"Priya Lakshminarayanan [MSFT]" <priyal@xxxxxxxxxxxxxxxxxxxx> wrote in
message news:424d97ef$1@xxxxxxxxxxxxxxxxxxxxx
> 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" <phatcher@xxxxxxxxxxxxxxxxxx> wrote in message
> news:%23cnymSuNFHA.1040@xxxxxxxxxxxxxxxxxxxxxxx
>> 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
>>
>>
>
>
.
- References:
- XmlValidatingReader memory behaviour
- From: Paul Hatcher
- Re: XmlValidatingReader memory behaviour
- From: Priya Lakshminarayanan [MSFT]
- XmlValidatingReader memory behaviour
- Prev by Date: Re: How to keep XSLs in Memory?
- Next by Date: Re: Loading XSL
- Previous by thread: Re: XmlValidatingReader memory behaviour
- Next by thread: Re: How to keep XSLs in Memory?
- Index(es):
Relevant Pages
|