T. M. Chilimbi, T. Ball, S. G. Eick, and J. R. . Larus. StormWatch: A Tool for Visualizing Memory System Protocols. In Supercomputing '95, December 1995. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
SIGMA: A Simulator Infrastructure to Guide Memory Analysis - DeRose, Ekanadham.. (2002) (3 citations) (Correct)
....hierarchy, but only relates this information back to program source lines, not to data structures. A system with more similarity to the techniques in this paper is MemSpy [21] which provides data oriented information as well as code oriented, but it uses simulation to collect its data. StormWatch [22] is another system that allows a user to study memory system interaction. It is used for visualizing memory system protocols under Tempest [23] a library that provides sotvare shared memory and message passing. However, the goal of StormWatch is to study how to adapt a memory system protocol to ....
T. M. Chilimbi, T. Ball, S. G. Eick, and J. R. Larus, "StormWatch: A Tool for Visualizing Memory System Protocols". In Proceedings of Supercomputing '95. December 1995, San Diego, CA.
Using Hardware Performance Monitors to Isolate Memory.. - Buck, Hollingsworth (2000) (4 citations) (Correct)
....hierarchy, but only relates this information back to program source lines, not data structures. A system with more similarity to the techniques in this paper is MemSpy [7] MemSpy provides data oriented information as well as code oriented, but uses simulation to collect its data. StormWatch [2] is another system that allows a user to study memory system interaction. It is used for visualizing memory system protocols under Tempest [9] a library that provides software shared memory and message passing. However, the goal of StormWatch is to study how to adapt a memory system protocol to ....
T. M. Chilimbi, T. Ball, S. G. Eick, and J. R. Larus, "StormWatch: A Tool for Visualizing Memory System Protocols," Supercomputing '95. December 1995, San Diego, CA.
Visual-MCM: Visualising Execution Histories on Multiple.. - Alba Cristina Melo (1999) (1 citation) (Correct)
....automatically or in a step by step basis. Figure 5 shows how a particular execution history is analysed on VisualMCM. Note that the analysis of possible execution paths depends only on the Memory Consistency Model. No particular implementations of memory models are considered. 5 Related Work [5] presents a visualisation tool called StormWatch. This tool is able to analyse the same application on different memory coherence protocols. StormWatch provides trace, source and communication views. The trace view is based on execution histories. Maya is a simulation platform described in [2] It ....
Chilimbi T., Ball T., Eick S., Larus J.: StormWatch: a Tool for Visualizing Memory System Protocols. Supercomputing'95 (1995).
Techniques and Tools for Distributed Shared Memory.. - Callaghan, Tamches (Correct)
....can be inferred from the visualizations. However, per cache block information is not provided, and access patterns that apply to a subset of cache blocks may be obscured. StormWatch displays event traces, and makes the trace display manageable by filtering events that a user is not interested in [Sto95]. However, patterns may only be interesting when they occur thousands of times and such a pattern may be difficult to see. Counts of events may be more suitable for some problems. Two protocols that avoid the write penalty for blocks that are accessed in a migratory pattern have been researched ....
T. M. Chilimbi, T. Ball, S. G. Eick, J. R. Larus, "StormWatch: A Tool for Visualizing Memory System Protocols," Submitted for publication, Supercomputing `95.
Understanding the Memory Behavior Performance on Software.. - Poulos (Correct)
....running programs to allow time for the search to converge and detect the bottlenecks. It s main limitation lies in the search along the why axis, where the main objective is to identify different types of overheads and not to provide causes for them that can be useful to the user. StormWatch [4] is a tool specifically targeted for software coherence protocols. It is actually a visualization tool and creates its displays using data from a program trace (containing protocol specific events) that is generated by the protocol itself. It provides three main views: a trace view, a source view, ....
T. M. Chilimbi, T. Ball, S. G. Eick and J. R. Larus. StormWatch: A Tool for Visualizing Memory System Protocols. In Proceedings of the 1995 International Conference on Supercomputing. May 1995.
Cause-Effect Analysis of Parallel Program Performance - Meira, Jr., LeBlanc (1997) (Correct)
....code and data structures. Although all of these tools give some insight into the causes of performance phenomena, the programmer is still responsible for the inference process that leads from observed effects to root causes. Some tools focus on a limited form of causality information. StormWatch [3] is a visualization tool for memory system protocols that captures relationships between individual memory events, thus exposing causality in memory operations. Another tool, a performance debugger implemented by Rajamony and Cox [10] automatically detects unnecessary and excessive ....
T. Chilimbi, T. Ball, S. Eick, and J. Larus. Stormwatch: A tool for visualizing memory system protocols. In Proceedings of Supercomputing'95, San Diego, CA, December 1995. IEEE.
Cause-Effect Analysis of Parallel Program Performance - Wagner Meira (Correct)
....code and data structures. Although all of these tools give some insight into the causes of performance phenomena, the programmer is still responsible for the inference process that leads from observed effects to root causes. Some tools focus on a limited form of causality information. StormWatch [3] is a visualization tool for memory system protocols that captures relationships between individual memory events, thus exposing causality in memory operations. Another tool, a performance debugger implemented by Rajamony and Cox [10] automatically detects unnecessary and excessive ....
T. Chilimbi, T. Ball, S. Eick, and J. Larus. Stormwatch: A tool for visualizing memory system protocols. In Proceedings of Supercomputing'95, San Diego, CA, December 1995. IEEE.
Shared-Memory Performance Profiling - Xu, Larus, Miller (1997) (9 citations) (Correct)
....extending the Performance Consultant to make it more configurable, so that we can specify search order, and search heuristics according to the programming model used. 6 Related Work In addition to the systems cited previously, several profiling tools address shared memory programs. StormWatch [4] is tool that visualizes coherence protocol actions and links it to a program s behavior. StormWatch provides three linked, graphic views: trace, communication, and source, which reflect the multiple levels of abstraction in an application s behavior. There are two major differences between our ....
T. M. Chilimbi, T. Ball, S. G. Eric, J. R. Larus. StormWatch: A Tool for Visualizing Memory System Protocols. Supercomputing'95, San Diego, CA, December, 1995.
Software Visualization in the Large - Ball, Eick (1996) (58 citations) Self-citation (Ball Eick) (Correct)
....between two procedures [Kri95] Run time behavior. Algorithm animation uses graphical representations of data structures and motion to illustrate the higher level behavior of algorithms [Bro88] Lower level views based on program profiles or traces can reveal bugs and performance anomalies [CBEL95]. The code itself. Pretty printers are a basic and widely used form of code visualization [BM90] Previous approaches to software visualization, although useful for small projects, do not scale to the production sized systems currently being manufactured. The graphical techniques found in ....
Trishul Chilimbi, Thomas Ball, Stephen G. Eick, and James R. Larus. Stormwatch: A tool for visualizing memory system protocols. In SuperComputing '95 (to appear), San Diego, California, December 1995.
Parallel Computer Research in the Wisconsin Wind Tunnel Project - Hill, Larus, Wood (1996) (2 citations) Self-citation (Larus) (Correct)
.... will develop their applications using transparent shared memory (obtained by linking their program with a standard protocol) After a program runs correctly, a programmer can improve its performance by selecting alternative library protocols to manage key data structures that are bottlenecks [14,7,9,35]. If no protocol performs well, the programmer can write a custom protocol for the program. Similarly, compilers can use custom protocols to implement higher level programming language constructs or optimize compiled programs [27] A commonly misunderstood aspect of Tempest is who in ....
Trishul Chilimbi, Thomas Ball, Stephen Eick, and James Larus. StormWatch: A Tool for Visualizing Memory System Protocols. In Proceedings of Supercomputing '95, December 1995.
PAT: A Postmortem Object Access Pattern Analysis and.. - Weijian Fang Cho-Li (Correct)
No context found.
T. M. Chilimbi, T. Ball, S. G. Eick, and J. R. . Larus. StormWatch: A Tool for Visualizing Memory System Protocols. In Supercomputing '95, December 1995.
Visualizing Execution Histories on Release Consistency and.. - Melo, Silva (Correct)
No context found.
T. Chilimbi, T. Ball, S. Eick, J. Larus, "StormWatch: a Tool for Visualizing Memory System Protocols", In Proc of Supercomputing'95 (1995).
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC