Ignore:
Timestamp:
Jan 30, 2013, 5:15:11 PM (7 years ago)
Author:
cameron
Message:

Abstract and conclusion

File:
1 edited

Legend:

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

    r2865 r2869  
    110110single-thread \icXML{}
    111111achieved about a 50\% acceleration over Xerces,
    112 increasing throughput on our test machine from ???  MB/sec to ??? MB/sec.   Using pipelined  \icXML{}, a
    113 further throughput increase to ???  MB/sec was recorded.
     112increasing throughput on our test machine from 58.3 MB/sec to 87.9 MB/sec.   Using pipelined  \icXML{}, a
     113further throughput increase to 111 MB/sec was recorded, approximately a 2X speedup.
    114114
    115115An important aspect of \icXML{} is the replacement of much branch-laden
    116116sequential code inside Xerces with straight-line SIMD code using far
    117117fewer branches.  Figure \ref{branchmiss_GML2SVG} shows the corresponding
    118 improvement in branching behaviour, with a dramatic reduction in branch misses per KB.
     118improvement in branching behaviour, with a dramatic reduction in branch misses per kB.
    119119It is also interesting to note that pipelined \icXML{} goes even
    120120further.   In essence, in using pipeline parallelism to split the instruction
     
    129129
    130130
    131 The behaviour of the three versions with respect to L1 cache misses per MB is shown
     131The behaviour of the three versions with respect to L1 cache misses per kB is shown
    132132in Figure \ref{cachemiss_GML2SVG}.   Improvements are shown in both instruction-
    133133and data-cache performance with the improveements in instruction-cache
Note: See TracChangeset for help on using the changeset viewer.