Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Francois Doray

dblp:193/3096 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 2017
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Computer architecture, parallel and distributed computing, and storage systems
1 paper
Performance modeling and evaluation · 100%
Software engineering, system software, and programming languages
1 paper
Operating systems · 100%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Performance modeling and evaluation
performance diagnosis
0.312017
Diagnosing Performance Variations by Comparing Multi-Level Execution Traces · IEEE Trans. Parallel Distributed Syst. 2017
Performance modeling and evaluation › performance variability
performance variance detection
0.312017
Diagnosing Performance Variations by Comparing Multi-Level Execution Traces · IEEE Trans. Parallel Distributed Syst. 2017
Operating systems › kernel instrumentation
kernel tracing
0.112017
Diagnosing Performance Variations by Comparing Multi-Level Execution Traces · IEEE Trans. Parallel Distributed Syst. 2017

Methods — techniques the papers use, named apart from their topics

trace comparison · 0.6execution tracing · 0.6calling context tree · 0.6
YearPublicationVenuePosition
2017 Diagnosing Performance Variations by Comparing Multi-Level Execution Traces
abstract
Tracing allows the analysis of task interactions with each other and with the operating system. Locating performance problems in a trace is not trivial because of their large size. Furthermore, deep knowledge of all components of the observed system is required to decide whether observed behavior is normal. We introduce TraceCompare, a framework that automatically identifies differences between groups of executions of the same task at the user space and kernel levels. Many performance problems manifest themselves as variations that are easily identified by our framework. Our comparison algorithm takes into account all threads that affect the completion time of analyzed executions. Differences are correlated with application code to facilitate the correction of identified problems. Performance characteristics of task executions are represented by a new data structure called enhanced calling context tree (ECCT). We demonstrate the efficiency of our approach by presenting four case studies in which TraceCompare was used to uncover serious performance problems in enterprise and open source applications, without any prior knowledge of their codebase. We also show that the overhead of our tracing solution is between 0.2 and 9 percent depending on the type of application.
Francois Doray, Michel R. Dagenais
IEEE Trans. Parallel Distributed Syst.1