1 / 15

Architectural Characterization of an IBM RS6000 S80 Server Running TPC-W Workloads

Architectural Characterization of an IBM RS6000 S80 Server Running TPC-W Workloads. Lei Yang & Shiliang Hu Computer Sciences Department, University of Wisconsin-Madison. Outline. TPC-W Benchmarks in Java IBM RS6000 S80 Enterprise Server Hardware Counters in S80 Experiment Results

debra
Download Presentation

Architectural Characterization of an IBM RS6000 S80 Server Running TPC-W Workloads

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Architectural Characterization of an IBM RS6000 S80 Server Running TPC-W Workloads Lei Yang & Shiliang Hu Computer Sciences Department, University of Wisconsin-Madison

  2. Outline • TPC-W Benchmarks in Java • IBM RS6000 S80 Enterprise Server • Hardware Counters in S80 • Experiment Results • Problems and Future work • Conclusions

  3. TPC-W benchmark • TPC-W is the TPC’s new benchmark for Transactional Web Environments (E-Commerce) Modeling an online book store similar to www.amazon.com • Browsing 95% browsing, 5% transactions • Shopping 80% browsing, 20% transactions • Ordering 50% browsing, 50% transactions • Transactional Web Environment: • Web serving of static and dynamic content • Online Transaction processing (OLTP) • Some decision support (DSS)

  4. IBM RS6000 S80 Enterprise Server • 6 RS64-III Pulsar processors (451MHz) • 4-issue in-order Super Scalar microprocessor with on chip 128KB L1 I-Cache, 128KB L1 D-Cache and 8MB L2 Cache. • No Branch Prediction, Aggressive early branch resolution • 2 coarse grain Multithreading. • SMP system. Snooping bus inter-processor connection. • 8GB main memory and large disk volumes. And high bandwidth IO systems.

  5. System Configuration: SUN Java Web Server2.0 Java Servlet http JDBC DB2 DBMS Processes Emulated Java Servlet Browser Java Virtual Machine Java Virtual Machine Performance Monitor Performance Monitor Performance Monitor Kernel Extension AIX kernel RS64-III processor RS64-III processor 32bits Control word 32bits Control word Snooping bus

  6. Hardware Counters in S80 • 3 major components - 8 Built-in hardware counters in each RS64-III processor. - Kernel extension to AIX 4.3 - Performance Monitor API in the next release of AIX. • 3 level counting with their own counting contexts: - System level counting, whole system level context - Process / Process group, process level context - Individual thread, thread level context. • Some Problems with current version. - Cannot counter for individual processor. - Some Listed events are not available.

  7. Hardware Counters in S80 • Processor events - execution cycles and the number of instructions executed. • Instruction mix events - Pipeline M, S, B and S instructions executed. • Branch events - Conditional branch T/NT events, unconditional branches, zero cycle branches. • Address Translation events - TLB/SLB and ERAT/IERAT miss and duration events. • Cache events - Cache misses and latencies for each of the L1 I-Cache L1 D-Cache L2 Cache • Bus and multi-processor bus snooping events - bus utilization. multi-processor bus snooping events

  8. Results: IPC for RBE, JavaWebServer and DB2

  9. Results: Instruction Dispatch

  10. Results: Instruction Mix

  11. Results: Branch Behavior

  12. Results: Cache Behavior

  13. Problems & Future Works • Problems: - Large Dataset - Network and Server end software are the bottleneck? - Hardware counters vs. Simulations. • Future works: - Measurement of other transactional processing and web serving benchmarks for comparison. -More architectural characterizations such as multithreaded processors, multiprocessor snooping and scaling.

  14. Conclusions • Server end Software is critical for high-end servers - Network and Server end software are the bottleneck - This is true for • Preliminary performance characterization shows: - CPU utilization is highly dependent upon the application workloads. - High dispatching mechanism on RS64III appears less efficiently used. - Branch behavior is web interactions dependent. - L2 cache miss rate is unreasonably low and

  15. Acknowledgement

More Related