Changes between Version 8 and Version 9 of Public/Energy

Timestamp:

Nov 19, 2020, 12:44:14 PM (3 years ago)

Author:

Alessio Netti

Comment:

—

Public/Energy

@@ -124 +124 @@
 * .med (median of all 10s measurements in a certain 30s time window)
 
-In order to get a cumulative measure of a job's performance (e.g., total energy spent or total amount of instructions computed), {{{.sum}}} should be used. Moreover, for a job to be measured by DCDB, its duration has to be longer than 30s.
+In order to get a cumulative measure of a job's performance (e.g., total energy spent or total amount of instructions computed), {{{.sum}}} should be used. Moreover, for a job to be measured by DCDB, its duration has to be longer than 30s. We currently expect to store job data for the entire lifetime of the system, and hence the time-to-live of 30 days does not apply to it.
 
 ==== Long-term Sub-sampled Sensor Data
 
-The sensor data collected by DCDB (including per-job data) has a time-to-live of 30 days. After this interval the data will be automatically erased from the database. However, to keep track of the system’s history, DCDB automatically computes sub-sampled versions of all sensors. These are kept forever in the database, and can be queried as follows:
+The sensor data collected by DCDB (excluding per-job data) has a time-to-live of 30 days. After this interval the data will be automatically erased from the database. However, to keep track of the system’s history, DCDB automatically computes sub-sampled versions of all sensors. These are kept forever in the database, and can be queried as follows:
 
 {{{