An integrated experimental environment for distributed systems and networks

By B. White, Jay Lepreau, L. Stoller, R. Ricci, Shashi Guruprasad, Mac Newbold, Mike Hibler, Charles E. Barb, Abhijeet Joglekar. USENIX Symposium on Operating Systems Design and Implementation, 2002

823 citations recorded by the source corpus.

Subfields: Computer Networks and Communications, Information Systems

View Paper: https://www.semanticscholar.org/paper/a67c68861aa85332ee30237e5b26b5ac0964c409

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

Making argument systems for outsourced computation practical (sometimes) (2012, methodology): “We run our experiments on Utah Emulab’s [72] d710s, which are 2.”
Test-case reduction for C compiler bugs (2012, methodology): “Some of our experiments were run on machines provided by the Utah Emulab testbed [16].”
In VINI veritas: realistic and controlled network experimentation (2006, background): “We have to ask if a programmable platform distributed over the whole nation is actually more realistic than backhauling end-user traffic to a central platform, like Emulab.”
SIMPLE-fying middlebox policy enforcement using SDN (2013, methodology): “We begin by running the topology from Figure 1 on different physical machines on the Emulab testbed.”
Serendipity: enabling remote computing among intermittently connected mobile devices (2012, methodology): “To evaluate Serendipity in various network settings, we have built a testbed on Emulab [33] to easily conﬁgure the experiment settings including the number of nodes, the node properties, etc.”
FlowVisor: A Network Virtualization Layer (2009, methodology): “[20, 23]) or by duplicating components in (often specialized) hardware[19].”
The Road to SDN (2013, background): “…interest in the idea of network experimentation at scale, encouraged by the success of experimental infrastructures (e.g., PlanetLab 6 and Emulab 83 ), and the availability of separate government funding for large-scale “instrumentation” previously reserved for other disciplines to build…”
PCC Vivace: Online-Learning Congestion Control (2018, methodology): “To demonstrate the effect of Vivace’s latency-aware and provably fair utility function framework, we evaluate (using Emulab) its throughput and latency performance on a link with 100 Mbps bottleneck bandwidth, 30 ms RTT, and varying buffer size.”
Dummynet revisited (2010, methodology): “Besides the use by individual researchers, Dummynet is also a core component in the popular Emulab [21] testbed, and has become extremely popular as a traﬃc shaper.”
Stronger Semantics for Low-Latency Geo-Replicated Storage (2013, neutral): “This experiment was run on PRObE’s Kodiak testbed [47], which provides an Emulab [59] with exclusive access to hundreds of machines.”
Depot: Cloud Storage with Minimal Trust (2010, methodology): “The nodes are part of a local Emulab [97], allowing us to vary the topology and performance of the network connecting them.”
Can the Production Network Be the Testbed? (2010, methodology): “Simulation [17, 19] and emulation [25] provide tightly controlled environments to run repeatable experiments, but lack scale and realism; they neither extend all the way to the end-user nor carry real user traffic.”
Datacenter RPCs can be General and Fast (2018, background): “CX4 and CX3 are CloudLab [54] and Emulab [63] clusters, respectively.”
Grid'5000: A Large Scale And Highly Reconfigurable Experimental Grid Testbed (2006, neutral): “Emulab (White et al. 2002) is another emulator, originally designed for network emulation.”
Astrolabe: A robust and scalable technology for distributed system monitoring, management, and data mining (2003, methodology): “For these experiments, we created the topology of Figure 11 in the Emulab network testbed [ White et al. 2002 ].”
Lessons Learned from the Chameleon Testbed (2020, methodology): “Unlike traditional CS experimental systems such as Grid’5000 [1], Emulab/CloudLab [2,3], or GENI [4], which have generally been conﬁgured by technologies developed in-house, Chameleon adapted the OpenStack mainstream open-source cloud technology to provide its capabilities.”
SHARP: an architecture for secure resource peering (2003, background): “, Content Services Networks), computational network overlays such as PlanetLab [36] and Netbed [48], peer-to-peer services, and grid computing systems, which harness federated computing resources for massive computational problems and network services [23].”
Operating Systems Support for Planetary-Scale Network Services (2004, methodology): “, by maintaining a per-vserver /etc/passwd and runningsshd on a different TCP port), thereby providing the basis for integration with oth er wide-area testbeds such as NetBed [42] and RON [1].”