Changeset 1115


Ignore:
Timestamp:
Apr 11, 2011, 3:07:28 PM (8 years ago)
Author:
ksherdy
Message:

Significant edits.

Location:
docs/PACT2011
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • docs/PACT2011/05-corei3.tex

    r1113 r1115  
    150150\includegraphics[width=0.5\textwidth]{plots/corei3_TOT.pdf}
    151151\end{center}
    152 \caption{Processing Time on \CITHREE\ (y-axis: Total CPU Cycles per kB)}
     152\caption{Processing Time on \CITHREE\ (y-axis: CPU Cycles per kB)}
    153153\label{corei3_TOT}
    154154\end{figure}
  • docs/PACT2011/06-scalability.tex

    r1114 r1115  
    11\section{Scalability}
    22\subsection{Performance}
    3 Figure \ref{Scalability} (a) shows the performance of Parabix2 on three different cores: \CO{}, \CITHREE\ and \SB{}.
    4 The average processing time of the five workloads, which is evaluated as CPU cycles per thousand bytes,
    5 is divided up by bitstream parsing and byte space postprocessing.
    6 Bitstream parsing, which mainly consists of SIMD instructions,
    7 is able to achieve 17\% performance improvement moving from \CO\ to \CITHREE{};
    8 22\% performance improvement moving from \CITHREE\ to \SB{},
    9 which is relatively stable compared to postprocessing,
    10 which gains 18\% to 31\% performance moving from \CO\ to \CITHREE{};
    11 0 to 17\% performance improvement moving from \CITHREE\ to \SB{}.
     3Figure \ref{Scalability} (a) demonstrates the average XML well-formedness checking performance of Parabix2 for each of the workloads and as executed on each of the processor cores --- \CO{}, \CITHREE\ and \SB{}.
     4Processing time is shown in terms of bit stream based operations executed in `bit-space' and postprocessing operations executed in `byte-space'.
     5In the Parabix2 parser, bit-space parallel bit stream parser operations consist primarily of SIMD instructions; byte-space operations
     6consist of byte comparisons across arrays of values. Executing Parabix2 on \CITHREE{} over \CO\ results in an average performance improvement
     7of 17\% in bit stream processing whereas migrating Parabix2 from \CITHREE{} to \SB{} results in a 22\% average performance gain. Bit space measurements are stable and consistent across each of the source inputs and cores. Postprocessing operations demonstrate data dependent variance. Performance gains from 18\% to 31\% performance are observered in migrating Parabix2 from \CO\ to \CITHREE{}; 0\% to 17\% performance
     8from \CITHREE\ to \SB{}. For the purpose of comparison, Figure \ref{Scalability} (b) shows the performance of the Expat parser on each of the processor cores.
     9A performance improvement of less than 5\% is observed when executing Expat on \CITHREE\ over \CO\
     10and less than 10\% on \SB\ over \CITHREE{}.
    1211
    13 As comparison, we also measured the performance of Expat on all the three cores, which is shown is Figure \ref{Scalability} (b).
    14 The performance improvement is less than 5\% by running Expat on \CITHREE\ instead of \CO\
    15 and it is less than 10\% by running on \SB\ instead of \CITHREE{}.
    16 
    17 Parabix2 scales much better than Expat and is able to achieve an overall performance improvement
    18 up to 26\% simply by running the same code on a newer core.
    19 Further improvement on \SB\ with AVX will be discussed in the next section.
     12Overall, Parabix2 scales better than Expat. Simply executing identical Parabix2 object code on \SB\ results in an overall performance improvement
     13up to 26\%. Additional performance aspects of Parabix2 on \SB\ with AVX instructions are discussed in the following sections.
    2014
    2115\begin{figure}
     
    2721\includegraphics[width=0.40\textwidth]{plots/Expat_scalability.pdf}
    2822}
    29 \caption{Performance Parabix vs. Expat (y-axis: Total CPU Cycles per kB)}
     23\caption{Average Performance Parabix vs. Expat (y-axis: CPU Cycles per kB)}
    3024\label{Scalability}
    3125\end{figure}
     
    3428\subsection{Power and Energy}
    3529
    36 The newer processors are not only designed to have better performance but also more energy-efficient.
    37 Figure \ref{power_Parabix2} shows the average power when running Parabix2 on \CO{}, \CITHREE\ and \SB\ with different input files.
    38 On \CO{}, the average power is about 32 watts. \CITHREE\ saves 30\% of the power compared with \CO{}.
     30Figure \ref{power_Parabix2} shows the average power consumption of Parabix2 over each workload and as executed on each of the processor cores --- \CO{}, \CITHREE\ and \SB\.
     31Average power consumption on \CO{} is 32 watts. Execution on \CITHREE\ results in 30\% power saving over \CO{}.
    3932\SB\ saves 25\% of the power compared with \CITHREE\ and consumes only 15 watts.
    4033
    41 The energy consumption is further improved by better performance, which means a shorter processing time, as we moved to the newer cores.
    42 As a result, Parabix2 on \SB\ cost 72\% to 75\% less energy than Parabix2 on \CO{}.
     34In XML parsing we observe energy consumption is dependent on processing time. That is, a reduction in processing time results in a directly proportional reduction in energy consumption.
     35With newer processor cores comes improvements in application performance. As a result, Parabix2 executed on \SB\ consumes 72\% to 75\% less energy than Parabix2 on \CO{}.
    4336
    4437\begin{figure}
  • docs/PACT2011/reference.bib

    r1114 r1115  
    11@inproceedings{CameronHerdyLin2008,
    2 author = {Cameron, Robert D. and Herdy, Kenneth S. and Lin, Dan},
     2author = {Cameron, Robert D. and Herdy, Kennrh S. and Lin, Dan},
    33title = {High performance {XML} parsing using parallel bit stream technology},
    44booktitle = {{CASCON} '08: Proceedings of the 2008 conference of the center for advanced studies on collaborative research},
Note: See TracChangeset for help on using the changeset viewer.