Performance debugging for distributed systems of black boxes

By Marcos Kawazoe Aguilera, Jeffrey C. Mogul, Janet L. Wiener, Patrick Reynolds, Athicha Muthitacharoen. Symposium on Operating Systems Principles, 2003

723 citations recorded by the source corpus.

Subfields: Computer Networks and Communications, Information Systems

View Paper: https://www.semanticscholar.org/paper/1602de4a38839633edf5c380453fddba13da2ce5

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Computer Networks and Communications

In Information Systems

Citations in the corpus

Dapper, a Large-Scale Distributed Systems Tracing Infrastructure (2010, background): “Black-box schemes [1, 15, 2] assume there is no additional information other than the message record described above, and use statistical regression techniques to infer that association.”
Towards highly reliable enterprise network services via inference of multi-level dependencies (2007, background): “Project5 [1] and WAP5 [16] record packet traces at each host and use message correlation algorithms to resolve which incoming packet triggered which outgoing packet.”
X-Trace: A Pervasive Network Tracing Framework (2007, neutral): “, in [1], find anomalous behavior in distributed systems by treating each component as a black box, and inferring the operation paths by only looking at message traces.”
Making Sense of Performance in Data Analytics Frameworks (2015, background): “Blocked time analysis lacks the sophistication and generality of general purpose distributed systems performance analysis tools (e.g., [5] [15] ), and unlike black-box approaches, requires adding instrumentation within the application.”
Carat: collaborative energy diagnosis for mobile devices (2013, background): “In order to determine the causal relationships among messages, Project5 [2] and WAP5 [38] use message traces and compute dependency paths.”
Capturing, indexing, clustering, and retrieving system history (2005, methodology): “This has been attempted in many domains including this one, most notably in [1].”
Correlating Instrumentation Data to System States: A Building Block for Automated Diagnosis and Control (2004, background): “[1] for an excellent review of these and related research efforts.”
/*icomment: bugs or bad comments?*/ (2007, background): “correctness) [12, 15, 23, 25, 37] are proposed to detect various types of software bugs.”
Understanding and detecting real-world performance bugs (2012, background): “Many previous works tried to isolate bottlenecks in (semi-) blackbox systems [1], correlate system metrics with performance behaviors [8, 48], avoid performance problems at runtime [52], and diagnose problems through logs [59].”
Pip: Detecting the Unexpected in Distributed Systems (2006, neutral): “Project 5 [1] infers causal paths from black-box network traces.”
Cloudward bound: planning for beneficial migration of enterprise applications to the cloud (2010, background): “Many research tools and commercial products can be used to obtain application dependencies either by inference from network communication patterns [13], or by analyzing application-level configurations [7, 21].”
Performance Measurement : Current Perspectives and Future Challenges (2006, neutral): “[1] draws our attention—they use a black box approach that finds the causal trace without any knowledge of the system, and a signal processing technique called convolution to infer causal relationships.”