This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Memory-saving Prescription for key()? [prompted by - RE: keys : repeated nodes from same key value]
- To: xsl-list at mulberrytech dot com
- Subject: RE: Memory-saving Prescription for key()? [prompted by - RE: keys : repeated nodes from same key value]
- From: John Robert Gardner <John dot Robert dot Gardner at East dot Sun dot COM>
- Date: Mon, 14 Aug 2000 10:20:35 -0400 (EDT)
- Reply-To: xsl-list at mulberrytech dot com
Thanks Mike, I was afraid of that.
jr
#From: Kay Michael <Michael.Kay@icl.com>
#To: "'xsl-list@mulberrytech.com'" <xsl-list@mulberrytech.com>
#Subject: RE: Memory-saving Prescription for key()? [prompted by - RE: keys :
repeated nodes from same key value]
#MIME-Version: 1.0
#
#Using key() will greatly reduce your search times, but it won't reduce the
#size of the tree in memory: on the contrary, it will increase it.
#
#Mike Kay
#
#> -----Original Message-----
#> From: John Robert Gardner [mailto:John.Robert.Gardner@East.Sun.COM]
#> Sent: 10 August 2000 17:49
#> To: xsl-list@mulberrytech.com
#> Subject: Memory-saving Prescription for key()? [prompted by -
#> RE: keys:
#> repeated nodes from same key value]
#>
#>
#> As long as we're on about keys . . . .
#>
#> I recall several comments, including in the venerable tome by
#> Michael, that
#> key's can be more efficient. My reason for asking is that I
#> have a repeated
#> set of information I ask for -- either
#>
#> match="//foo[*[contains(name(), 'bar')
#> and contains(., 'my_string')]]">
#>
#> -or-
#>
#> match="//foobar[*[contains(name(), 'barfoo')
#> and contains(., 'my_string')]]">
#>
#> In other words, the element type name changes a lot, and the
#> element type name string for
#> contains(name(), 'whatever') changes between only one or two
#> values, and 'my_string'
#> always stays the same.
#>
#> I've got only 5.6 megs of data, and the element type names
#> are HUGE (it's XMI stuff
#> from the MOF for some class diagrams) . . . my DOM tree is
#> bloating to 150 megs,
#> and I'm looking to trim down my memory footprint . . . is
#> this a proper diagnosis
#> for key()? I could make a key for the contains(name(),
#> 'barfoo'), contains(name(),
#> 'bar'), and contains(., 'my_string'), if my guess is right?
#>
#> ----------------------------------
#> John Robert Gardner, Ph.D.
#> Enterprise Management Architecture
#> Sun Microsystems
#> Burlington, MA 01803
#> <remote />
#>
#>
#> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
#>
#
#
# XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-|
John Robert Gardner, Ph.D.
Enterprise Management Architecture Group
Sun Microsystems Inc.,
MailStop UBUR03-316
1 Network Drive
Burlington, MA 01803-0903 | "Earn this"
|
Ph. 781-442-0692 | -Capt. John H. Miller
Fax 781-442-1539 | Saving Private Ryan
e-mail john.robert.gardner@sun.com
-----------------------------------
http://vedavid.org/diss/
http://vedavid.org/xml/docs/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list