I don't know if the LenB function would work on the DOM object, but you could always try it.
A couple of years ago, I witnessed IE consuming over 120 Mb of memory (according to Task Manager) trying to open a 3.6 Mb XML document before the presenter killed it. I'm sure a some or a lot of that may have been IE's presentation logic parsing the DOM, but it also makes me leery about large DOM's. Therefore - test early. Although not a finely tuned instrument for memory allocation, Task Manager will give you a reasonable idea about the impact you'll see. Find or build a reasonably large (according to your intended app) XML document, start your app, check its memory usage by Task Manager, load the XML into a DOM in the app, and see how much additional memory was required.. HTH, Tore. ----- Original Message ----- From: "Kevin Collins" <[EMAIL PROTECTED]> To: "ActiveServerPages" <[EMAIL PROTECTED]> Sent: Monday, October 28, 2002 11:58 AM Subject: Re: Measuring memory used in application variables > > The in-memory representation of the DOM can get quite large, even for a > > limited amount of data. You may want to do some measurements on that before > > you get too deeply invested. > > > > As for the data itself, a VB[S] string's total length is 8 + LenB(s). The 8 > > bytes are: 4 bytes for a pointer to the string storage, and 4 bytes to > > describe the length of the string. > > So how would I measure the in-memory representation of the data if it's > cached as a free-threaded DOMDocument, as opposed to a string? > > Does the lenb() function still work? > > Thanks, > Kevin > > --- > You are currently subscribed to activeserverpages as: [EMAIL PROTECTED] > To unsubscribe send a blank email to %%email.unsub%% > --- You are currently subscribed to activeserverpages as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED]
