diff --git a/docs/hyperloop/hyperlooppolicy.md b/docs/hyperloop/hyperlooppolicy.md index 9b9b3b6b..80b3503c 100644 --- a/docs/hyperloop/hyperlooppolicy.md +++ b/docs/hyperloop/hyperlooppolicy.md @@ -43,3 +43,17 @@ Derived datasets can be created on Hyperloop which are by construction much smal As an example, you can imagine that you run a derived data train on a dataset of 500 TB where you need explicit approval. Say you have a reduction factor of 100, then your output derived data is about 5 TB. You will be allowed to run on that dataset much more frequent, see the table above. However, it may be that your analysis remains CPU hungry even if the input dataset is reduced. By default the operators who create your dataset will assign the resources based on the table above. The person who has requested the dataset can request to change that assignement. This will increase the CPU limit but reduce the trains/week and auto-submission slots by moving down one row in the table above. Obviously, running on a derived dataset should never take more resources than the limits that apply to the original parent dataset. + +The image below summarizes an advantage of derived data: +
+