Wallclock time and the output size scale linearly in the number of
events for most Mu2e jobs. One can estimate the slope and the
intercept by running jobs of increasing length (the -n
option to mu2e). The /usr/bin/time utility
(not just "time"!) is useful to measure the memory consumption:
/usr/bin/time mu2e -c test.fcl -n 10 ... Art has completed and will exit with status 0. 28.07user 2.41system 0:43.59elapsed 69%CPU (0avgtext+0avgdata 3836928maxresident)k 3003072inputs+112outputs (9463major+210992minor)pagefaults 0swaps
From the above output, we conclude that the test job used
3836928 / 4096 = 937 MB of memory. (SL6 is shipped with
a buggy version of GNU time, this is why we need to divide the
reported size by 4096 instead of 1024 for the purported "k" units.)
One caveat is that estimates can be affected by large rare events, which may not be seen in short jobs.
|
|
| Security, Privacy, Legal |
|
