Ignore:
Timestamp:
Oct 20, 2012, 12:30:32 PM (7 years ago)
Author:
nmedfort
Message:

edits

File:
1 edited

Legend:

Unmodified
Added
Removed
  • docs/Working/icXML/conclusion.tex

    r2512 r2522  
    1 \section{Conclusion and Future Work}
    2 
    31This paper presented the \icXML{} parser and discussed the key architectural differences between it and Xerces.
    42\icXML{} was architected to utilize SIMD parallelism, facilitated by the Parabix framework. \icXMLp{} extended on
     
    119Although only a two-thread version was explored, more is possible---but the value of using more is dependent on
    1210the application utilizing the \icXML{} library.
    13 As the application becomes more complex there are diminishing returns w.r.t. additional thread-level parallelism.
     11As the application becomes more complex there are diminishing returns \wrt{} additional thread-level parallelism.
    1412A more interesting use of additional threads could be in the inclusion of an XPath and XQuery modules that could
    1513eliminate unneeded data prior to the \MP{} stage.
Note: See TracChangeset for help on using the changeset viewer.