1. UPC/SHMEM PAT High-level Design v.1.1 Hung-Hsun Su UPC Group, HCS lab 6/21/2005

2. High-level Design

3. Instrumentation Units Automatic source instrumentation manager – deals with the system- assisted instrumentation of source code [i.e. all source level instrumentation except line-by-line instrumentation done by the user]. This determines what to instrument and how to instrument it from the manual instrumentation configuration [for user defined constructs] and automatic instrumentation configuration [for all upc and shmem constructs]. Binary Instrumentation manager – responsible for adding binary instrumentation to the object code. It also includes the capability of performing dynamic instrumentation at the binary level.

4. Measurement Units Measurement modules – perform the actual measurement of events either through software or hardware (most likely HW specific). They make calls to the low-level event write module to actually record the basic event data. Low-level event read/write modules – responsible for reading/writing low-level (raw, basic) event data to a storage space (file for tracing, memory for profiling). Event file manager – primarily used to merge all basic event data from all nodes into a single event file (needed to handle the case where a single event file will be too big). The sub-module trace format converter is responsible for converting from one trace format to another.

5. Analysis Units High-level event module – provides methods to access basic and complex event data. It calls the low-level event read module to access the basic event data. It includes an aggregation module to produce complex event data and a search/indexing module for efficient accessing of both the basic and complex event data. Simulator – provides simulation support using the event data.

6. Analysis Units Analysis modules – each module is responsible for performing and generating the necessary data for a specific analysis.  Standard analysis modules - basic load balancing analysis (ex: % busy), multiple runs data comparison  Advanced analysis modules - advanced load balancing analysis (ex: best scheduling analysis), scalability analysis, memory system analysis.  Other analysis modules - performance prediction, based-line execution time calculation, bottleneck detection, bottleneck management, bottleneck resolution (manual and automatic).

7. Analysis Units Analysis/data manager – interface to access all types of data (basic, complex, and analysis data). It uses high-level event module to read basic and complex event data. It also provides the mechanism for invoking the appropriate analysis modules based on the default view configuration and view configuration to produce appropriate analysis data (supplies the invoked analysis module with necessary data). The sub-module search module provides the capability for searching analysis data and basic/complex data (through calls to the high-level event module). Finally, it supplies the visualization manager with all or a subset of the various data generated. The other sub-module, performance data manager, is responsible for more advanced data management

8. Presentation Units Input interface – text-based (command line) and graphic-based (GUI) interface for performing tasks that can be done before [instrumenting the code, selecting views] and after [selecting additional views, data processing operations] running the program. Design of the GUI depends solely on the Command line interface.

9. Presentation Units Visualization manager – responsible for producing the various views (standard views, advanced views, plug-in views). Each module interacts only with the analysis/data manger to obtain all or a subset of the data (can cause analysis/data manager to invoke analysis modules). Has the capability of relating views together that affects the amount of data received from the analysis/data manager  Standard view modules - timeline display, call graph tree, speedup chart, communication volume display, and array placement display.  Advanced view modules – TBD.  Plug-in view modules - plug-in views defined by the user [an interface will be defined on how to add new plug-in view modules].

10. Flow Diagram