Find research datasets worth reusing

Edge infrastructure traces

<p>These Edge infrastructure traces consist of bandwidth and latency between devices along with the execution time of the microservices of a video processing application on the different devices. These traces were collected between 2022-10-24 and 2022-11-09.</p> <p>The execution times are related to a set of microservices, including video encoding and framing, along with the training and inference model for road sign classification.<br>The microservices' descriptions are provided in the following research paper:<br>N. Mehran, Z. N. Samani, D. Kimovski, and R. Prodan, "Matching-based Scheduling of Asynchronous Data Processing Workflows on the Computing Continuum," 2022 IEEE International Conference on Cluster Computing (CLUSTER), 2022, pp. 58-70, DOI: 10.1109/CLUSTER51413.2022.00021.</p> <p><br>Devices are as follows:<br>- D01 machine has a twelve-core AMD Ryzen Threadripper 2920X processor with 32GB memory;<br>- D02 machine has an eight-core Intel Core(TM) i7-7700 processor with 16GB memory;<br>- Nvidia Jetson Nano machine has a four-core ARM Cortex-A72 processor with 4GB memory;<br>- Raspberry Pi 4 has a four-core ARM Cortex A57 processor with 4GB of memory.</p> <p>Moreover, the dataset provides the network traces regarding the bandwidth and latency between the Edge devices. We provided the size of the transmitted messages between the devices for the throughput measurements. For the network latency, the information related to the round trip time is calculated by ICMP message request and reply.</p> <p>The traces include five parts of data as follows:</p> <p>BW-MessageSize.csv<br>- Timestamp: Date and time in CET<br>- Source device: the throughput from which we are checking; D02 machine<br>- Destination device: the throughput to which we are checking; D01 or D02 machine<br>- Message size (MB): the message size transmitted between the devices<br>- BW (Mbps): the maximum achievable bandwidth<br>*** "-1" means "iperf3: error - unable to connect to server: Connection refused"</p> <p>&nbsp;</p> <p>JetsonNano-ExecutionTime.csv<br>- Timestamp: Date and time in CET<br>- Device: the Nvidia Jetson Nano single-board computer<br>- Microservice: includes encoding, framing, training, or inference of Dockerized microservices<br>- Execution Time (seconds)</p> <p><br>Large-ExecutionTime.csv<br>- Timestamp: Date and time in CET<br>- Device: the highest performance machine (D01 machine) in the C3 testbed<br>- Microservice: includes encoding, framing, training, or inference (containers)<br>- Execution time (seconds)</p> <p>&nbsp;</p> <p><br>Latency.csv<br>- Timestamp: Date and time in CET<br>- Source device: the latency from which we are checking; D02 machine<br>- Destination device: the latency to which we were checking; D01 or D02 machine<br>- Minimum latency (ms) of the round-trip times among four transmitted messages<br>- Average latency (ms) of the round-trip times among four transmitted messages<br>- Maximum latency (ms) of the round-trip times among four transmitted messages<br>- Mean standard deviation of the round-trip times among four transmitted messages</p> <p>&nbsp;</p> <p><br>RPi4-ExecutionTime.csv<br>- Timestamp: Date and time in CET<br>- Device: Raspberry Pi v4 single-board computer<br>- Microservice: includes encoding, framing, training, or inference (containers)<br>- Execution time (seconds)</p> <p>&nbsp;</p> <p>For more information regarding the testbed, please refer to the C3 website at https://c3.itec.aau.at/.</p> <p><br>Authors:<br>Zahra Najafabadi Samani, Narges Mehran, Dragi Kimovski, Josef Hammer, Radu Prodan<br>Institute of Information Technology, Alpen-Adria-Universitaet Klagenfurt, Austria</p> <p><br>&nbsp;</p>