Parallel Performance Wizard 1.2 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Parallel Performance Wizard 1.2 (Default branch)
# 1  
Old 10-02-2008
Parallel Performance Wizard 1.2 (Default branch)

Parallel Performance Wizard (PPW) is a performance analysis tool designed for UPC, MPI, and SHMEM programs. It features an easy-to-use interface and tight integration with GAS programming models via the GASP interface. It is known to work on many platforms. This project is part of a study of existing and emerging performance analysis theory and tools, current and future HPC architectures, and usability and user productivity preferences and methods, along with various programming models. License: BSD License (revised) Changes:
Assorted fixes and minor updates. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Help need to improve performance :Parallel processing ideas

Hi, Please tell me how to include parallel processing for the below code. Thanks in advance I have a list of users directories in root directory. Each user has a directory by his /her username. I am finding the size of each directorry using du -g command.. and checking if the size exceeds 3GB a... (6 Replies)
Discussion started by: justchill
6 Replies
Login or Register to Ask a Question
PMDASYSTEMTAP(1)					       Performance Co-Pilot						  PMDASYSTEMTAP(1)

NAME
pmdasystemtap - Systemtap performance metrics domain agent (PMDA) DESCRIPTION
pmdasystemtap is a Performance Metrics Domain Agent (PMDA) which exports metric values from the Linux Systemtap dynamic tracing toolkit. This implementation uses the stap(1) tool, which is a front-end to the Systemtap toolkit. INSTALLATION
In order to access performance data exported by Systemtap from with PCP, it is necessary to perform two configuration steps: 1. Configure Systemtap probes, and verify them with stap(1). These should be produced in a format that is easily parsed, and then stored in the $PCP_PMDAS_DIR/systemtap/probes.stp file. 2. Configure pmdasystemtap to extract the values from the text produced by stap. Two example probes are implemented in the default systemtap PMDA script - readdir and sync traces (see $PCP_PMDAS_DIR/systemtap/pmdasystemtap.pl for details). # cd $PCP_PMDAS_DIR/systemtap # [ edit probes.stp, test /usr/bin/stap probes.stp ] # [ edit pmdasystemtap.pl ] Once this is setup, you can access the names and values for the systemtap performance metrics by doing the following as root: # cd $PCP_PMDAS_DIR/systemtap # ./Install If you want to undo the installation, do the following as root: # cd $PCP_PMDAS_DIR/systemtap # ./Remove pmdasystemtap is launched by pmcd(1) and should never be executed directly. The Install and Remove scripts notify pmcd(1) when the agent is installed or removed. FILES
$PCP_PMDAS_DIR/systemtap/probes.stp probe configuration file for stap(1), run by pmdasystemtap $PCP_PMDAS_DIR/systemtap/Install installation script for the pmdasystemtap agent $PCP_PMDAS_DIR/systemtap/Remove undo installation script for the pmdasystemtap agent $PCP_LOG_DIR/pmcd/systemtap.log default log file for error messages from pmdasystemtap SEE ALSO
pmcd(1) and stap(1). 3.8.10 Performance Co-Pilot PMDASYSTEMTAP(1)