Skip to content

Commit a862f7a

Browse files
authored
Update README.md
1 parent 9bf632f commit a862f7a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/faq/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ necessarily need to be duplicated. For an example, please check
2525

2626
### I haven't changed anything but sometimes my wagon test gives a memory warning and sometimes not, and also the estimated resources change somewhat.
2727

28-
We base the measurement of used memory and CPU on a 3 minute O2 execution with your task. Depending on how the different processes of O2 interact the memory consumption can slightly vary. If your task is just at the limit, this can result sometimes in a warning and sometimes not. Similarly, the estimated CPU is calculated from the short test and then scaled to the entire dataset. Already slight changes in execution time can have a big impact and therefore the numbers are not the same on each test. The best is to not operate at the memory / CPU limit and so you do not get any warnings.
28+
We base the measurement of used memory and CPU on a 3 minute O2 execution with your task. Depending on how the different processes of O2 interact the memory consumption can slightly vary. If your task is just at the limit, this can result sometimes in a warning and sometimes not. Similarly, the estimated CPU is calculated from the short test and then scaled to the entire dataset. Already slight changes in execution time can have a big impact and therefore the numbers are not the same on each test. The best is to not operate close to the memory / CPU limit and so you do not get any warnings. You can inspect the history of all your tests in the wagon modal by clicking on the tab 'test statistics'.
2929

3030
### Why do different wagon tests on the same data process a different number of input files?
3131

0 commit comments

Comments
 (0)