[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

memory efficiency of xslt wrt to element and attribute names?

• From: Nicholas Sushkin <nsushkin@openfinance.com>
• To: xml-dev@lists.xml.org
• Date: Fri, 9 Jul 2010 10:17:49 -0400

"Don't abbreviate without necessity" principle has been on my mind for quite a 
while. However, I always thought of memory consumption. Say you're 
transforming an XML file with 1 million P2E elements with XSLT processor. 
There is a big difference in memory consumption between the two element name 
styles. <P2E>20</P2E> vs <price-to-earnings-ratio value="20"/> is 5 vs 30 
characters and, since XSLT builds the whole tree in memory which say takes 4 
times the size of the file, about 20Mb vs 120Mb. Why wouldn't you save 
yourself some memory and trouble?

My question, is my reasoning still valid or it's been outdated by some 
improvements in memory efficiency of XSLT processors?

Thanks
-- 
Nick

On Tuesday, July 06, 2010 19:27:30 Amelia A Lewis wrote:
> On Mon, 05 Jul 2010 15:22:13 -0400, ycao5@scs.carleton.ca wrote:
> >     I have a basic question for xml and xslt. The xml element node
> > 
> > name contains a "/". For example, an xml element node
> > (price-to-earnings ratio) is represented as P/E. The xml parser will
> > throw an exception for "/" follows P. How to correctly represent the
> > tag name containing "/"?
> 
> While <P/E> is not legal XML, <price-to-earnings> is.  So is
> <price-to-earnings-ratio>.
> 
> dnt abrvt wo ncsty
> 
> Amy!

smime.p7s

• Follow-Ups:
  • Re: memory efficiency of xslt wrt to element and attributenames?
    • From: David Carlisle <davidc@nag.co.uk>
  • Re: memory efficiency of xslt wrt to element and attributenames?
    • From: David <dlee@calldei.com>

• References:
  • Re: How to represent P/E correctly?
    • From: Amelia A Lewis <amyzing@talsever.com>