Artifact Evaluation Guide

Welcome to the artifact evaluation guide for Atropos (SOSP'25). This document outlines the procedures needed to reproduce our results and guides you through the key experiments presented in the paper.

Overview

Atropos is an overload control system designed to manage application resource overload by proactively canceling tasks responsible for monopolizing critical resources. It achieves this by continuously monitoring resource usage, identifying tasks causing significant resource contention, and selectively canceling them to maintain performance targets. Atropos provides unified abstractions to manage diverse application resources and leverages existing cancellation mechanisms in applications to safely kill problematic requests.

Getting Started

Cloning the Repository

git clone --recurse-submodules [email protected]:OrderLab/Atropos.git

Updating Submodules

If you already have the repository cloned but need to update the submodules:

git submodule update --init --recursive

To pull the latest changes from all submodules:

git submodule update --remote

Project Structure

The artifact is organized into the following main components:

Core Implementation

• project/atropos-c/ - C/C++ Atropos library and system integrations

  • atropos/ - Core Atropos library implementation
  • atropos-apache/ - Modified Apache HTTP Server with Atropos support
  • atropos-mysql/ - Modified MySQL database with Atropos integration
  • atropos-postgresql/ - Modified PostgreSQL database with Atropos support
  • sysbench-atropos/ - Sysbench for performance evaluation

• project/atropos-java/ - Java-based implementation and benchmarks

  • atropos_java_code/ - Java Atropos library
  • atropos_exp/ - Experimental evaluation code
  • elasticsearch/ - Elasticsearch integration and benchmarks
  • solr/ - Apache Solr integration and benchmarks
  • scripts/ - Utility scripts for experiments and evaluation

Each component includes its own build instructions and documentation. Refer to the individual README files in each directory for specific setup and usage instructions.

Prerequisites

Before proceeding with the experiments, ensure you have the following installed:

• Operating System: Linux (Ubuntu 18.04+ recommended) or macOS
• Languages & Runtimes:
  • GCC/Clang (for C/C++ components)
  • Java 8+ (for Java components)
  • Python 3.6+ (for scripts and utilities)
• Build Tools:
  • CMake 3.10+
  • Make
  • Maven or Gradle (for Java builds)
• Dependencies:
  • MySQL development libraries
  • PostgreSQL development libraries
  • Apache HTTP Server development headers

Important Note on Hardware and Performance Dependencies

The resource overload cases and bug reproduction are highly dependent on specific hardware and software configurations. Performance characteristics vary significantly across different machines, which affects the timing and conditions required to trigger the resource overload scenarios.

If you are using your own machine (not our pre-configured environment):

• You will need to fine-tune the bug reproduction scripts located in the cases/ folder
• Scripts may require adjustment of timing parameters, workload intensities, or resource thresholds
• After you successfully trigger the resource overload condition, you can follow our instructions to run Atropos

Pre-tuned Machine Configurations: We have successfully tuned and tested the reproduction scripts on the following machine configurations:

• Available Machines

For the most reliable evaluation experience, we recommend using our pre-configured evaluation environment.

Experiments

C Experiments Setup & Execution Guide

Java Experiments Setup & Execution Guide

Citation

If you use this artifact in your research, please cite our paper:

@inproceedings{atropos2025,
  title={Atropos: A Library for Mitigating Application Resource Overload},
  author={[Authors]},
  booktitle={Proceedings of the 30th ACM Symposium on Operating Systems Principles},
  series={SOSP '25},
  year={2025},
  publisher={ACM}
}

Contact

For questions about this artifact or the paper, please contact:

• [email protected]
• Open an issue in this repository for technical problems

License

This project is licensed under [License to be specified]. See individual component directories for specific licensing information.