Changeset 2516 for docs/Working/icXML


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

Updates, more streams to discuss

Location:
docs/Working/icXML
Files:
4 edited

Legend:

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

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

    r2505 r2516  
    11\subsection{Overview}
     2\begin{figure}
     3\begin{center}
     4\includegraphics[width=0.15\textwidth]{plots/xerces.pdf}
     5\caption{Xerces Architecture}
     6\label{fig:xerces-arch}
     7\end{center}
     8\end{figure}
    29
    310\icXML{} is more than an optimized version of Xerces. Many components were grouped, restructured and
     
    2633
    2734\begin{figure}
    28 \begin{center}
    29 \includegraphics[width=0.15\textwidth]{plots/xerces.pdf}
    30 \caption{Xerces Architecture}
    31 \label{fig:xerces-arch}
    32 \end{center}
     35\includegraphics[width=0.50\textwidth]{plots/icxml.pdf}
     36\caption{\icXML{} Architecture}
     37\label{fig:icxml-arch}
    3338\end{figure}
    3439
     
    8085the majority of the grammar look-ups are performed beforehand and stored within the symbol themselves.
    8186
    82 \begin{figure}
    83 \includegraphics[width=0.50\textwidth]{plots/icxml.pdf}
    84 \caption{\icXML{} Architecture}
    85 \label{fig:icxml-arch}
    86 \end{figure}
    8787
    8888% 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 r2516  
    5858Start Tag Marks & \verb`_1_____1____________1________________________________1_____________________`\\
    5959End Tag Marks & \verb`_______________1________________________________1____________________1_____`\\
     60Empty Tag Marks & \verb`___________________________________________________________________1_______`\\
    6061Element Names & \verb`_1111__11___________11_______________________________1111__________________`\\
    6162Att Names & \verb`_______________________11_______11________________________1111_____________`\\
    62 Att Values & \verb`__________________________11111______11111_____________________111_________`
     63Att Values & \verb`___________________________111________111_______________________1__________`\\
     64String ends & \verb`1_____1_______1____1__________1__________1_____1____1____________1__1______`\\
     65String marks & \verb`0_____0_______0____0__________0__________0_____0____0____________0__0______`\\
     66Transition marks & \verb`_____1___1_____1_________1_________1______1_____1_____________1____1_1_____`\\
     67Transition chars & \verb`_____>___>_____/_________=_________=______>_____/_____________=____>_/_____`\\
     68Deletion mask & \verb`_1111__11_______111_11111_1____1111_11___________111_111111111_1__1___11111`\\
     69Undeleted & \verb`_____>___>text_/_________=_foo_____=__fie_>more_/_____________=_b__>_/_____`
    6370\end{tabular}
    6471\end{center}
  • docs/Working/icXML/icxml-main.tex

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