Well, I was simply responding to this in your note: "The reason I ask is because recently my inbox exploded due to an error on the server which resulted in error emails being send out and the error just so happened to be on a page where there was a large XML object (I output all available variables/scopes to the error email in order to have the best chance of diagnosing / repeating errors). I was just wondering was the email so big because the XML had be parsed? I'm now going to have to find some way of removing all XML objects from each scope before dispatching an error email... any ideas?"
It just really sounded like your focus was on the big email that had the dumps of the objects. For that, I'd argue that would be still MUCH bigger in bytes than either the source or the internal object. But if you really mean what you say here, about "Lets say you are storing the XML in the session scope, would it be better to store parsed XML or the original XML", then I'll agree with you both that it seems possible that the internal object rendered from an XMLParse could take up more space in bytes in memory than the source XML. It's just a guess, though, and it may vary depending on some factors that may not be well understood without our knowing more of the internals of CF and how it renders things internally. Since there's no way to ask CF "how large is the object tree created for this varable", it's a tough one to know for sure. If you're on CF8 Enterprise or Developer, you could enable the memory tracking in the Server Monitor (don't do this in production), which will tell you how large variables (and I assume their assocated object graphs for complex variables) are. /charlie -----Original Message----- From: cfaussie@googlegroups.com [mailto:cfaus...@googlegroups.com] On Behalf Of Matthew Sent: Tuesday, January 20, 2009 11:54 PM To: cfaussie Subject: [cfaussie] Re: Is XML bigger before or after XmlParse @Dale: your thoughts seem to confirm mine, that's 2 vs 0. @Charlie: not really. I am interested in how much memory the before and after XML takes up. Lets say you are storing the XML in the session scope, would it be better to store parsed XML or the original XML... no doubt it depends on how many times would you be XmlParse() ing the session variable. Perhaps if you intended on parsing the XML variable 10 times it would be better to parse it then store it versus if you only intended to parse it once than it's better to store it un- parsed. On a website that gets a lot of traffic if you store the XML parsed it would take up a lot more space. Anyone else? Cheers Matthew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
