Vista - Generally accepted file size threshold of XmlDocument?

04-09-2009

I have a test file that contains 3.28 MB with 10,000 entries that will need
to be parsed. What is --generally-- considered an acceptable file size
threshold
when working with the XmlDocument?

04-09-2009

Hillbilly wrote:

Quote:

> I have a test file that contains 3.28 MB with 10,000 entries that will need
> to be parsed. What is --generally-- considered an acceptable file size
> threshold
> when working with the XmlDocument?

Whatever fits in your server's memory and offers acceptable loading times.
Try it out!

Less flippantly, there's little point in pinning down a fixed size where
XmlDocument is "acceptable". If you already know you are going to be
processing big files (or files that are potentially unlimited in size,
anyway), go with XmlReader and/or XPathDocument from the start, as unlike
XmlDocument they scale. This isn't much harder than using XmlDocument,
unless you need in-memory editing, in which case it's slightly trickier --
you'll have to weigh the added development time against the need for scaling.

Even for small documents where XmlDocument could be used, XElement is cooler
still. XmlDocument's DOM approach is rather clumsy.

--
J.

04-09-2009

XElement has an in-memory model too but looks easier to read once its
written that can be said. Thaks for reminding me...

"Jeroen Mostert" <jmostert@xxxxxx> wrote in message
news:49de34cb$0$193$e4fe514c@xxxxxx

Quote:

> Hillbilly wrote:

Quote:

>> I have a test file that contains 3.28 MB with 10,000 entries that will
>> need
>> to be parsed. What is --generally-- considered an acceptable file size
>> threshold
>> when working with the XmlDocument?

>
> Whatever fits in your server's memory and offers acceptable loading times.
> Try it out!
>
> Less flippantly, there's little point in pinning down a fixed size where
> XmlDocument is "acceptable". If you already know you are going to be
> processing big files (or files that are potentially unlimited in size,
> anyway), go with XmlReader and/or XPathDocument from the start, as unlike
> XmlDocument they scale. This isn't much harder than using XmlDocument,
> unless you need in-memory editing, in which case it's slightly trickier --
> you'll have to weigh the added development time against the need for
> scaling.
>
> Even for small documents where XmlDocument could be used, XElement is
> cooler still. XmlDocument's DOM approach is rather clumsy.
>
> --
> J.

04-09-2009	#1 (permalink)
Hillbilly n/a posts	Generally accepted file size threshold of XmlDocument? I have a test file that contains 3.28 MB with 10,000 entries that will need to be parsed. What is --generally-- considered an acceptable file size threshold when working with the XmlDocument?
My System Specs

04-09-2009	#2 (permalink)
Jeroen Mostert n/a posts	Re: Generally accepted file size threshold of XmlDocument? Hillbilly wrote: Quote: > I have a test file that contains 3.28 MB with 10,000 entries that will need > to be parsed. What is --generally-- considered an acceptable file size > threshold > when working with the XmlDocument? Whatever fits in your server's memory and offers acceptable loading times. Try it out! Less flippantly, there's little point in pinning down a fixed size where XmlDocument is "acceptable". If you already know you are going to be processing big files (or files that are potentially unlimited in size, anyway), go with XmlReader and/or XPathDocument from the start, as unlike XmlDocument they scale. This isn't much harder than using XmlDocument, unless you need in-memory editing, in which case it's slightly trickier -- you'll have to weigh the added development time against the need for scaling. Even for small documents where XmlDocument could be used, XElement is cooler still. XmlDocument's DOM approach is rather clumsy. -- J.
My System Specs

04-09-2009	#3 (permalink)
Hillbilly n/a posts	Re: Generally accepted file size threshold of XmlDocument? XElement has an in-memory model too but looks easier to read once its written that can be said. Thaks for reminding me... "Jeroen Mostert" <jmostert@xxxxxx> wrote in message news:49de34cb$0$193$e4fe514c@xxxxxx Quote: > Hillbilly wrote: Quote: >> I have a test file that contains 3.28 MB with 10,000 entries that will >> need >> to be parsed. What is --generally-- considered an acceptable file size >> threshold >> when working with the XmlDocument? > > Whatever fits in your server's memory and offers acceptable loading times. > Try it out! > > Less flippantly, there's little point in pinning down a fixed size where > XmlDocument is "acceptable". If you already know you are going to be > processing big files (or files that are potentially unlimited in size, > anyway), go with XmlReader and/or XPathDocument from the start, as unlike > XmlDocument they scale. This isn't much harder than using XmlDocument, > unless you need in-memory editing, in which case it's slightly trickier -- > you'll have to weigh the added development time against the need for > scaling. > > Even for small documents where XmlDocument could be used, XElement is > cooler still. XmlDocument's DOM approach is rather clumsy. > > -- > J.
My System Specs

Similar Threads
Thread	Forum
Xmldocument encoding question.	.NET General
Change threshold on Resource Exhaustion Detector and Resolution(RA	Vista performance & maintenance
XmlDocument SelectSingleNode doesn't work	PowerShell
ADO and XmlDocument cmdlets?	PowerShell
server working for me now, but getting incorrect file size on file	Vista General