gtcasl / eiger Goto Github PK

View Code? Open in Web Editor NEW

1.0 3.0 1.0 9.51 MB

Home page for the Eiger statistical performance modeling framework.

Home Page: http://gpuocelot.gatech.edu/projects/eiger/

License: Other

Shell 0.09% C++ 0.77% C 91.34% Python 1.40% Makefile 0.01% M4 0.24% Objective-C 6.16%

eiger's Introduction

Eiger Performance Modeling Framework

Overview

This document gives a brief overview into the stucture and installation of the Eiger performance modeling framework. More details can be found in the documentation folder.

Folder Layout

./api - The Eiger C++ API
./database - sqlite3 schema for Eiger database
./documentation - Documentation describing the implementation of Eiger
./eiger - Eiger performance modeling framework
./examples - Examples of basic modeling functionality
./tests - Simple tests ensuring correct installation of Eiger

Please review the requirements specification in the ./documentation folder for all required software packages.

Usage

All metric collection, model generation, polling, serialization, and reporting functionality can be installed with the following command:

python setup.py install

They can be controlled by the Eiger.py script; more information can be found by entering the following command after installing:

Eiger.py -h

As well, the Eiger module can be imported and used to issue any of the same commands used by the command line script. Examples of basic modeling functions can be found in the ./examples folder.

Database Setup

The Eiger modeling framework relies upon a sqlite3 relational database to manage metric storage, model construction, and model serialization. All data used by sqlite3 is contained in a single database file. If a filename is provided which has not been used for storing Eiger data, it will be converted into one.

API Installation

The API is built using the standard Autotools workflow:

    ./bootstrap.sh
    ./configure
    make
    make install

Run ./configure --help for more information.

Example Data

Several sets of example data reside in the ./examples subdirectory. This data was used for different publications and may or may not retain their functionality as Eiger is developed.

`lwperf`

Lwperf is a lightweight C/C++/Fortran profiling tool that allows for dumping of output files either to CSV, Eiger database, or serialization format for later injection into an Eiger database. Please see the documentation in the lwperf project for more information.

eiger's People

Contributors

Stargazers

Watchers

Forkers

hoangt

eiger's Issues

structs can't be used as parameters at log sites

Elements of structs do not seem able to be directly used by lwperf. For example, the following code does not work:

opts.nx = 30;
PERFLOG(somesitename, IP(opts.nx)) fails with an error about the variable not being declared

but,

opts.nx = 30;
int q = opts.nx;
PERFLOG(somesitename, IP(q));

works just fine.

Bitbucket: https://bitbucket.org/eanger/eiger/issue/8
Originally reported by: pierrelaborde
Originally created at: 2013-10-16T19:13:17.833

lwperf: commented out profiling calls are used

lwperf does not care if a profiling site is commented out, it tries to log it anyway. A poorly constructed lwperf call that is commented out will still generate compilation errors.

Bitbucket: https://bitbucket.org/eanger/eiger/issue/7
Originally reported by: pierrelaborde
Originally created at: 2013-10-16T19:01:10.171

Output model files with appropriate name.

Instead of having the user specify what the file name should be when outputting a model, we should just use the data collection name with a suffix like ".model". This way we can synchronize the lwperf instrumentation, model generation, and interface within SST/macro.

Bitbucket: https://bitbucket.org/eanger/eiger/issue/4
Originally reported by: Eric Anger
Originally created at: 2013-09-30T17:32:28.068

verbose logging

Flag to turn on verbose logging in Eiger.py would be nice.

Bitbucket: https://bitbucket.org/eanger/eiger/issue/5
Originally reported by: Eric Anger
Originally created at: 2013-10-07T16:39:45.909

Fails on multiple result metrics

Trying to train on multiple result metrics fails with cryptic error about matrices not lining up.

Bitbucket: https://bitbucket.org/eanger/eiger/issue/1
Originally reported by: Eric Anger
Originally created at: 2013-09-04T21:32:58.289

No install rules for api

There are no rules in the Makefile in the api directory to install the libraries or binaries.

Bitbucket: https://bitbucket.org/eanger/eiger/issue/2
Originally reported by: Eric Anger
Originally created at: 2013-09-18T20:52:30.259

lwperf calls should automatically inject model polling calls

lwperf calls added to applications already have all the information necessary to inject polling calls for SSTmacro polling. Perhaps a flag set for lwperf that tells it you're using sstmacro and desire poll calls to be added, which may also include some way to turn them on/off.

Bitbucket: https://bitbucket.org/eanger/eiger/issue/3
Originally reported by: Eric Anger
Originally created at: 2013-09-18T22:35:48.993

Dumping model files doesn't record cluster centroids

The model files don't contain centroid information for determining which model to poll when using kmeans clustering.

Bitbucket: https://bitbucket.org/eanger/eiger/issue/6
Originally reported by: Eric Anger
Originally created at: 2013-10-07T22:45:24.238

The line continuation character breaks lwperf

For example, the following code does not work:

PERFLOG(SITENAME, IP(its), IP(nx), IP(numReg), IP(numFiles), IP(showProg),
IP(quiet), IP(viz), IP(balance), IP(cost));