Re: XMLDOM overheads (was RE: FN-FORUM ASP Question - Simple I hope.)

date posted 17th January 2002 21:45

you cant just test like with like here, anyone who tries should try talking
from the mouth instead of the arse. (xecuse any spelling - im pissed)

ADO is *very* intensive - its extremely feature rich - you check the
performance with a C++ app using ADO for a simple query and OLE DB with ADO
you;ll see a large performance difference. not so much in VB, but thats VB
for you.

heres a few tips:
xmldom as a *single* object is has less overheads than ADO - for example
loading an xml document is less trouble then loading a recordset - for an
ecommerce site for example.

updating a database transactionally is easier in ADO, xml is a twat-about
with that by fannying around with the free-threading version.

dont use text files anymore - xmldom supercedes them in both ease of use and
performance.

have a look at how often your db server is accessed, and then at your web
server - by placing more load on the least called-on improves performance
in many cases, if possible use sql server to generate xml to get the best of
both worlds.

you *cannot* say which is better ADO or XML without first looking ast the
set-up - different configsd generate different resultd
----- Original Message -----
From: "Norman Beresford" [EMAIL REMOVED]
To: [EMAIL REMOVED]
Sent: Thursday, January 17, 2002 11:42 AM
Subject: XMLDOM overheads (was RE: FN-FORUM ASP Question - Simple I hope.)


> Hi all
>
> A couple of you have mentioned the overheads of using the XMLDom to parse
> XML files and as I've just started playing with them I wondered if you'd
go
> into a bit more detail on them. I've got a couple of projects requiring
> some data access. As I see it I've got three alternatives:
>
> a textfile using FSO
> an XML document using XMLDOM
> a DB call using ADO
>
> Two of the projects I'm doing involve pulling out a single node/record of
> information. In one (the BOFH thing), it's just a random node/record,
while
> in the other (a calender type app), it's a node/record with a specific
date.
> Now usually I would use ADO and a DB, but I wanted to get some XML stuff
> underway. What I'm bascially after is which would be the fastest solution
> in the above two cases. Does XMLDOM have any advantages over ADO for
local
> data, or does it only really come into it's own for using other people's
> data?
>
> Norman
>
>
>
>
> > -----Original Message-----
> > From: [EMAIL REMOVED]
> > [EMAIL REMOVED] Behalf Of Matthew Reynolds
> > Sent: 17 January 2002 11:23
> > To: [EMAIL REMOVED]
> > Subject: RE: FN-FORUM ASP Question - Simple I hope.
> >
> >
> > In classic ASP, I'd be a little concerned about the overhead required to
> > parse the XML file. I'd almost suggest a "huge case statement"
> > was the way to go.
>
>
> ============================================================
> = Get your message here for as little as £1 per week =
> = =
> = http://www.freelancers.net/cgi/sponsor.cgi?action=show =
> ============================================================
>
> * Free listing for freelancers
> * Free to advertise jobs
> * Free jobs distribution service
> * Free database of 5000 freelancers
>
> Freelancers and Freelance Jobs:
> http://www.freelancers.net
>
> Forum FAQs:
> http://freelancers.netrickery.com
>
> To unsubscribe please email:
> [EMAIL REMOVED]
>
> If you have difficulties unsubscribing please email:
> [EMAIL REMOVED]