# Changeset 2516 for docs

Ignore:
Timestamp:
Oct 20, 2012, 6:59:02 AM (6 years ago)
Message:

Location:
docs/Working/icXML
Files:
4 edited

Unmodified
Removed
• ## docs/Working/icXML/abstract.tex

 r2294 Using SIMD techniques alone, an increase in parsing speed of 50\% to 100\% was observed in a range of applications. When coupled with pipeline parallelism on multicore processors, improvements up to 3X were realized. When coupled with pipeline parallelism on dual core processors, improvements approaching 3X were realized.
• ## docs/Working/icXML/arch-overview.tex

 r2505 \subsection{Overview} \begin{figure} \begin{center} \includegraphics[width=0.15\textwidth]{plots/xerces.pdf} \caption{Xerces Architecture} \label{fig:xerces-arch} \end{center} \end{figure} \icXML{} is more than an optimized version of Xerces. Many components were grouped, restructured and \begin{figure} \begin{center} \includegraphics[width=0.15\textwidth]{plots/xerces.pdf} \caption{Xerces Architecture} \label{fig:xerces-arch} \end{center} \includegraphics[width=0.50\textwidth]{plots/icxml.pdf} \caption{\icXML{} Architecture} \label{fig:icxml-arch} \end{figure} the majority of the grammar look-ups are performed beforehand and stored within the symbol themselves. \begin{figure} \includegraphics[width=0.50\textwidth]{plots/icxml.pdf} \caption{\icXML{} Architecture} \label{fig:icxml-arch} \end{figure} % Probably not the right area but should we discuss issues with Xerces design that we tried to correct?
• ## docs/Working/icXML/background-parabix.tex

 r2512 Start Tag Marks & \verb_1_____1____________1________________________________1_____________________\\ End Tag Marks & \verb_______________1________________________________1____________________1_____\\ Empty Tag Marks & \verb___________________________________________________________________1_______\\ Element Names & \verb_1111__11___________11_______________________________1111__________________\\ Att Names & \verb_______________________11_______11________________________1111_____________\\ Att Values & \verb__________________________11111______11111_____________________111_________ Att Values & \verb___________________________111________111_______________________1__________\\ String ends & \verb1_____1_______1____1__________1__________1_____1____1____________1__1______\\ String marks & \verb0_____0_______0____0__________0__________0_____0____0____________0__0______\\ Transition marks & \verb_____1___1_____1_________1_________1______1_____1_____________1____1_1_____\\ Transition chars & \verb_____>___>_____/_________=_________=______>_____/_____________=____>_/_____\\ Deletion mask & \verb_1111__11_______111_11111_1____1111_11___________111_111111111_1__1___11111\\ Undeleted & \verb_____>___>text_/_________=_foo_____=__fie_>more_/_____________=_b__>_/_____ \end{tabular} \end{center}
• ## docs/Working/icXML/icxml-main.tex

 r2512 differences between the two parsing models.   Section 3 then presents the \icXML{} design based on a restructured Xerces architecture to incorporate SIMD parallelism using Parabix methods.   Section 4 presents a performance study demonstrating substantial end-to-end acceleration of incorporate SIMD parallelism using Parabix methods. Section 4 moves on to consider the multithreading of the \icXML{} architecture using the pipeline parallelism model. Section 5 analyzes the performance of both the single-threaded and multi-threaded versions of \icXML{} in comparison to original Xerces, demonstrating substantial end-to-end acceleration of a GML-to-SVG translation application written against the Xerces API. Section 5 moves on to consider the multithreading of the \icXML{} architecture using the pipeline parallelism model.  Section 6 concludes the Section 6 concludes the paper with a discussion of future work and the potential for applying the techniques discussed herein in other application domains.
Note: See TracChangeset for help on using the changeset viewer.