blob: ec5782cb5518224c6e69c071e4432d5b7494eb63 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
|
### Traces
OpenDC works with two types of traces that describe the servers that need to be run. Both traces have to be provided as
parquet files.
#### Meta
The meta trace provides an overview of the servers:
| Metric | Datatype | Unit | Summary |
|--------------|------------|----------|--------------------------------------------------|
| id | string | | The id of the server |
| start_time | datetime64 | datetime | The submission time of the server |
| stop_time | datetime64 | datetime | The finish time of the submission |
| cpu_count | int32 | count | The number of CPUs required to run this server |
| cpu_capacity | float64 | MHz | The amount of CPU required to run this server |
| mem_capacity | int64 | MB | The amount of memory required to run this server |
#### Trace
The Trace file provides information about the computational demand of each server over time:
| Metric | Datatype | Unit | Summary |
|-----------|------------|---------------|---------------------------------------------|
| id | string | | The id of the server |
| timestamp | datetime64 | datetime | The timestamp of the sample |
| duration | int64 | milli seconds | The duration since the last sample |
| cpu_count | int32 | count | The number of cpus required |
| cpu_usage | float64 | MHz | The amount of computational power required. |
|
