Power, L. R., "Design and use of a program execution analyzer," IBM Systems Journal, vol. 22, no. 3, pp. 271-294, 1983. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Performance Evaluation for Parallel Systems: A Survey - Hu, Gorton (1997) (2 citations) (Correct)
....Quite often, to make the evaluation results more convincing to the system s user, these techniques can be used together. In the literature, there have appeared a number of excellent survey papers which review the work in a particular aspect discussed above. For example, Plattner81] and [Power83] are program execution monitor survey papers. Plattner and Nievergelt survey the development of program execution monitors, and discuss basic concepts and requirements, design considerations for monitoring languages, and implementation and timing aspects. Power focuses on program execution ....
....to specific system points (the connections are made with probes) where they detect signals characterizing the phenomena to be observed [Ferrari83] A hybrid monitor is a combination of software and hardware. Many examples of software monitors can be found in the literature (see e.g. Plattner81; Power83; Malony92] Examples of hardware monitors are 26 COMTEN and SPM [Ibbett78] Ries93] describes the Paragon performance monitoring environment that uses a hardware performance monitoring board. And examples of hybrid monitors are Diamond [Hughes80] and HMS [Hadsell83] Each class of monitors ....
[Article contains additional citation context not shown here]
Power, L. R., "Design and use of a program execution analyzer," IBM Systems Journal, vol. 22, no. 3, pp. 271-294, 1983.
Profiling Prolog Programs - Debray (1983) (1 citation) (Correct)
....in only marginal improvements to the performance of the program. The implementation of profilers for traditional languages appears to be well understood, because of the relatively simple flow of control in such languages. Execution profilers for such languages often rely on sampling techniques [9, 11]; others maintain runtime counts that record the total number of times each program statement is executed ( 12] see also [1] With the increasing popularity of logic programming languages like Prolog, and the increasing volume of code being written in such languages, the need for profiling tools ....
L. R. Power, Design and Use of a Program Execution Analyzer, IBM Systems Journal 22, 3 (1983), pp. 271-294.
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