[
Lists Home |
Date Index |
Thread Index
]
At 9:37 PM -0400 4/13/04, Stephen D. Williams wrote:
>Example workloads:
>
>create document, insert elements/attributes/values linearly, randomly, reverse
>output document
>
>input document, read sequentially, randomly, reverse
>
>input document, perform various read/update/delete ratios
>output result
>
>input document, take pieces of input and create new outputs
>output results
>
>input document, create new version as a delta
>output document, delta
>
>input document, delta, perform read/update/delete, insert, append
>output new delta
In practice input and output are the only things that matter.
Compared to this all manipulations of XML in memory are in the noise
by several orders of magnitude. Optimizing read, update, delete,
insert, etc. is pointless. These things all happen in effectively
zero time compared to parsing, serialization, and sometimes the
program's unique algorithms. (If the input is an XML document
containing 5000 cities for which to solve the travelling salesman
problem, no XML optimization will help you.) But the XML
manipulations and traversal are trivial.
--
Elliotte Rusty Harold
elharo@metalab.unc.edu
Effective XML (Addison-Wesley, 2003)
http://www.cafeconleche.org/books/effectivexml
http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA
|
