Testbed dataset for "Waiting at the front door: Continuous monitoring of latency in the host network stack"

This is the dataset from the experiments in the local testbed of the "Waiting at the front door: Continuous monitoring of latency in the host network stack" paper. The data includes both load-generator (oha) results, the netstacklat measurements on the DuT, and a number of system-wide metrics (CPU and network metrics from Prometheus node-exporter) across all 3 hosts in the testbed (load-generator, DuT, and origin-server). The code used to generate and analyze the dataset is available here. Data format Each individual workload experiment generates a folder with thefollowing contents: oha_results.json: The measurement results from the oha load generator (as produced by its "--output-format json" option) prometheus_metrics/ <prometheus_metric>.json: List of JSON files with metrics exported from Prometheus' query-range API. The name of the file (without the ".json" suffix) corresponds to the Prometheus metric name (e.g. node_cpu_seconds_total) ... These result folders make up the leaf-folders in the dataset. The name of the parent folders encode the workload parameters of the test (which is automatically parsed by the analysis code). E.g. the "tool=pwru/run=3/server_config=apache.revproxy:4343/request=pi_10k/concurrent_connections=100" folder contains the results from the third test iteration of the Apache reverse proxy configuration fetching the pi_1k.html (10kB of pi digits) resource with 100 concurrent connections while pwru is running on the DuT. Hosts Several of the Prometheus metrics (all system metrics, the netstacklat and eBPF metrics are only available on the DuT) include instances from all 3 hosts. These are how the instances map to the 3 hosts in the testbed: instance: 192.168.60.186:<port>: The load generator instance: 192.168.60.239:<port>: The DuT instance: 192.168.60.225:<port>: The origin server (only relevant for the reverse proxy configurations) Manifest The dataset contains results from 3 sets of experiments. httpworkloads_netstacklat_test/20251103: The 144 different workload combinations that netstacklat was evaluated with (Section 5 in the paper). httpworkloads_multitool_overhead_test/: Contains experiments where multiple different monitoring tools were used on the DuT to assess their overhead. 20251105: 9 repetitions of tests using the nginx server configuration and serving 10kB files (Section 6 in the paper). multiworkloads_20251107: Single repetition of tests using the nginx server, nginx reverse proxy, and Apache server configurations with 1kB and 1MB files. A verification experiment to ensure that results from the 20251105 run generalizes across different workload scenarios (only briefly mentioned in the paper).