- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -
- Information contained in the HLRS Wiki is not legally binding and HLRS is not responsible for any damages that might result from its use -
Kojak: Difference between revisions
From HLRS Platforms
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Infobox software | |||
| description = '''KOJAK''' is a performance-analysis tool for parallel applications supporting the programming models MPI, OpenMP, SHMEM, and combinations thereof. Its functionality addresses the entire analysis process including instrumentation, post-processing of performance data, and result presentation. It is based on the idea of automatically searching event traces of parallel applications for execution patterns indicating inefficient behavior. The patterns are classified by category and their significance is quantified for every program phase and system resource involved. The results are made available to the user in a flexible graphical user interface, where they can be investigated on varying levels of granularity. | |||
| developer = Jülich Supercomputing Centre, Innovative Computing Laboratory | |||
| available on = | |||
| category = [[:Category:Performance Analysis Tool | Performance Analysis Tool]] | |||
| license = Proprietary | |||
| website = [http://icl.cs.utk.edu/kojak/ KOJAK homepage] | |||
}} | |||
== External links == | == External links == | ||
* [http://icl.cs.utk.edu/kojak/ KOJAK homepage] | * [http://icl.cs.utk.edu/kojak/ KOJAK homepage] | ||
[[Category:Performance Analysis Tool]] | |||
Revision as of 16:28, 24 February 2010
| KOJAK is a performance-analysis tool for parallel applications supporting the programming models MPI, OpenMP, SHMEM, and combinations thereof. Its functionality addresses the entire analysis process including instrumentation, post-processing of performance data, and result presentation. It is based on the idea of automatically searching event traces of parallel applications for execution patterns indicating inefficient behavior. The patterns are classified by category and their significance is quantified for every program phase and system resource involved. The results are made available to the user in a flexible graphical user interface, where they can be investigated on varying levels of granularity. |
| ||||||||||||