Pre-processed Tracing Data for Popular Microservice Benchmarks
Cite this dataset:
Qiu, Haoran; Banerjee, Subho S.; Jha, Saurabh; Kalbarczyk, Zbigniew T.; Iyer, Ravishankar K. (2020): Pre-processed Tracing Data for Popular Microservice Benchmarks. University of Illinois at Urbana-Champaign. https://doi.org/10.13012/B2IDB-6738796_V1
Use this persistent URL to link to this dataset:
Dataset Description

We are releasing the tracing dataset of four microservice benchmarks deployed on our dedicated Kubernetes cluster consisting of 15 heterogeneous nodes. The dataset is not sampled and is from selected types of requests in each benchmark, i.e., compose-posts in the social network application, compose-reviews in the media service application, book-rooms in the hotel reservation application, and reserve-tickets in the train ticket booking application.

The four microservice applications come from [DeathStarBench](https://github.com/delimitrou/DeathStarBench) and [Train-Ticket](https://github.com/FudanSELab/train-ticket). The performance anomaly injector is from [FIRM](https://gitlab.engr.illinois.edu/DEPEND/firm.git).

The dataset was preprocessed from the raw data generated in FIRM's tracing system. The dataset is separated by on which microservice component is the performance anomaly located (as the file name suggests). Each dataset is in CSV format and fields are separated by commas. Each line consists of the tracing ID and the duration (in 10^(-3) ms) of each component. Execution paths are specified in `execution_paths.txt` in each directory.

Subject Technology and Engineering
Keywords Microservices; Tracing; Performance
License CC0
Corresponding Creator Haoran Qiu
Downloaded 787 times
Version DOI Comment Publication Date
1 10.13012/B2IDB-6738796_V1 2020-08-22
Open in Globus File Manager what's this?
2.98 GB File

Contact the Research Data Service for help interpreting this log.

update: {"nested_updated_at"=>[Thu, 18 Apr 2024 18:23:36.977668000 UTC +00:00, Thu, 18 Apr 2024 18:23:38.852158000 UTC +00:00]} 2024-04-18T18:23:38Z
update: {"nested_updated_at"=>[Mon, 01 Apr 2024 17:02:42.421000000 UTC +00:00, Thu, 18 Apr 2024 18:23:36.977668000 UTC +00:00]} 2024-04-18T18:23:36Z
update: {"nested_updated_at"=>[Mon, 01 Apr 2024 17:02:42.321930000 UTC +00:00, Mon, 01 Apr 2024 17:02:42.421000000 UTC +00:00]} 2024-04-01T17:02:42Z
update: {"nested_updated_at"=>[Mon, 01 Apr 2024 17:00:18.425337000 UTC +00:00, Mon, 01 Apr 2024 17:02:42.321930000 UTC +00:00]} 2024-04-01T17:02:42Z
update: {"nested_updated_at"=>[Mon, 01 Apr 2024 17:00:18.396503000 UTC +00:00, Mon, 01 Apr 2024 17:00:18.425337000 UTC +00:00]} 2024-04-01T17:00:18Z
update: {"nested_updated_at"=>[Mon, 01 Apr 2024 17:00:18.371730000 UTC +00:00, Mon, 01 Apr 2024 17:00:18.396503000 UTC +00:00]} 2024-04-01T17:00:18Z
update: {"nested_updated_at"=>[Mon, 01 Apr 2024 17:00:18.346428000 UTC +00:00, Mon, 01 Apr 2024 17:00:18.371730000 UTC +00:00]} 2024-04-01T17:00:18Z
update: {"nested_updated_at"=>[Mon, 01 Apr 2024 17:00:18.319873000 UTC +00:00, Mon, 01 Apr 2024 17:00:18.346428000 UTC +00:00]} 2024-04-01T17:00:18Z
update: {"nested_updated_at"=>[Mon, 01 Apr 2024 17:00:18.242772000 UTC +00:00, Mon, 01 Apr 2024 17:00:18.319873000 UTC +00:00]} 2024-04-01T17:00:18Z
update: {"nested_updated_at"=>[Mon, 01 Apr 2024 17:00:18.213488000 UTC +00:00, Mon, 01 Apr 2024 17:00:18.242772000 UTC +00:00]} 2024-04-01T17:00:18Z
update: {"nested_updated_at"=>[Mon, 01 Apr 2024 17:00:18.184332000 UTC +00:00, Mon, 01 Apr 2024 17:00:18.213488000 UTC +00:00]} 2024-04-01T17:00:18Z
update: {"nested_updated_at"=>[Mon, 01 Apr 2024 17:00:18.154217000 UTC +00:00, Mon, 01 Apr 2024 17:00:18.184332000 UTC +00:00]} 2024-04-01T17:00:18Z
update: {"nested_updated_at"=>[Mon, 01 Apr 2024 17:00:18.120475000 UTC +00:00, Mon, 01 Apr 2024 17:00:18.154217000 UTC +00:00]} 2024-04-01T17:00:18Z
update: {"nested_updated_at"=>[Mon, 01 Apr 2024 17:00:18.067978000 UTC +00:00, Mon, 01 Apr 2024 17:00:18.120475000 UTC +00:00]} 2024-04-01T17:00:18Z
update: {"nested_updated_at"=>[Sun, 13 Nov 2022 03:02:54.002711000 UTC +00:00, Mon, 01 Apr 2024 17:00:18.067978000 UTC +00:00]} 2024-04-01T17:00:18Z
update: {"nested_updated_at"=>[nil, Sun, 13 Nov 2022 03:02:54.002711000 UTC +00:00]} 2024-01-03T18:23:47Z
update: {"description"=>["We are releasing the tracing dataset of four microservice benchmarks deployed on our dedicated Kubernetes cluster consisting of 15 heterogeneous nodes. The dataset is not sampled and is from selected types of requests in each benchmark, i.e., compose-posts in the social network application, compose-reviews in the media service application, book-rooms in the hotel reservation application, and reserve-tickets in the train ticket booking application.\r\n\r\nThe four microservice applications come from [DeathStarBench](https://github.com/delimitrou/DeathStarBench) and [Train-Ticket](https://github.com/FudanSELab/train-ticket). The performance anomaly injector is from [FIRM](https://github.com/James-QiuHaoran/firm).\r\n\r\nThe dataset was preprocessed from the raw data generated in FIRM's tracing system. The dataset is separated by on which microservice component is the performance anomaly located (as the file name suggests). Each dataset is in CSV format and fields are separated by commas. Each line consists of the tracing ID and the duration (in 10^(-3) ms) of each component. Execution paths are specified in `execution_paths.txt` in each directory.\r\n", "We are releasing the tracing dataset of four microservice benchmarks deployed on our dedicated Kubernetes cluster consisting of 15 heterogeneous nodes. The dataset is not sampled and is from selected types of requests in each benchmark, i.e., compose-posts in the social network application, compose-reviews in the media service application, book-rooms in the hotel reservation application, and reserve-tickets in the train ticket booking application.\r\n\r\nThe four microservice applications come from [DeathStarBench](https://github.com/delimitrou/DeathStarBench) and [Train-Ticket](https://github.com/FudanSELab/train-ticket). The performance anomaly injector is from [FIRM](https://gitlab.engr.illinois.edu/DEPEND/firm.git).\r\n\r\nThe dataset was preprocessed from the raw data generated in FIRM's tracing system. The dataset is separated by on which microservice component is the performance anomaly located (as the file name suggests). Each dataset is in CSV format and fields are separated by commas. Each line consists of the tracing ID and the duration (in 10^(-3) ms) of each component. Execution paths are specified in `execution_paths.txt` in each directory.\r\n"]} 2020-10-20T17:26:15Z
update: {"description"=>["We are releasing the tracing dataset of four microservice benchmarks deployed on our dedicated Kubernetes cluster consisting of 15 heterogeneous nodes. The dataset is from selected types of requests in each benchmark, i.e., compose-posts in the social network application, compose-reviews in the media service application, book-rooms in the hotel reservation application, and reserve-tickets in the train ticket booking application.\r\n\r\nThe four microservice applications come from [DeathStarBench](https://github.com/delimitrou/DeathStarBench) and [Train-Ticket](https://github.com/FudanSELab/train-ticket). The performance anomaly injector is from [FIRM](https://github.com/James-QiuHaoran/firm).\r\n\r\nThe dataset was preprocessed from the raw data generated in FIRM's tracing system. The dataset is separated by on which microservice component is the performance anomaly located (as the file name suggests). Each dataset is in CSV format and fields are separated by commas. Each line consists of the tracing ID and the duration (in 10^(-3) ms) of each component. Execution paths are specified in `execution_paths.txt` in each directory.\r\n", "We are releasing the tracing dataset of four microservice benchmarks deployed on our dedicated Kubernetes cluster consisting of 15 heterogeneous nodes. The dataset is not sampled and is from selected types of requests in each benchmark, i.e., compose-posts in the social network application, compose-reviews in the media service application, book-rooms in the hotel reservation application, and reserve-tickets in the train ticket booking application.\r\n\r\nThe four microservice applications come from [DeathStarBench](https://github.com/delimitrou/DeathStarBench) and [Train-Ticket](https://github.com/FudanSELab/train-ticket). The performance anomaly injector is from [FIRM](https://github.com/James-QiuHaoran/firm).\r\n\r\nThe dataset was preprocessed from the raw data generated in FIRM's tracing system. The dataset is separated by on which microservice component is the performance anomaly located (as the file name suggests). Each dataset is in CSV format and fields are separated by commas. Each line consists of the tracing ID and the duration (in 10^(-3) ms) of each component. Execution paths are specified in `execution_paths.txt` in each directory.\r\n"]} 2020-08-22T19:28:31Z