- jwebb's home page
- Posts
- 2019
- 2018
- 2017
- 2016
- 2015
- 2014
- 2013
- November (1)
- October (1)
- September (1)
- July (1)
- June (1)
- April (1)
- March (3)
- February (1)
- January (1)
- 2012
- 2011
- December (2)
- September (3)
- August (5)
- July (6)
- June (6)
- May (1)
- April (5)
- March (5)
- February (2)
- January (2)
- 2010
- December (3)
- October (3)
- September (2)
- August (2)
- June (2)
- May (4)
- April (4)
- March (2)
- February (4)
- January (10)
- 2009
- 2008
- 2007
- 2006
- July (1)
- My blog
- Post new blog entry
- All blogs
MC Request for BES
Time and disk footprint estimates for the BES request. Spreadsheet is attached.
| Time | |||
| starsim: | 646.85 | CPU wk | |
| bfchain: | 3389.29 | CPU wk | |
| total: | 4036.13 | CPU wk | |
| Footprint: | |||
| (1) Everything | 30.48 | TB | |
| (2) Smallest | 7.11 | TB | |
| +McEvent | 6.19 | TB | |
| +MuDst | 0.92 | TB | |
- Request is larger than the available resources: ~1TB and 1 CPU wk.
- We cannot store "everything" on disk. Can the requestors make do with just the MuDst and McEvent files? geant.root would nearly double the size, and the fzd files will need to be sent straight to HPSS (or perhaps not even saved).
- Even then the request is too large.
- Proposal: reduce request by factor of 1/4. This yields:
- ~0.25 M at 39 GeV / ~0.4 M at 11.5 GeV / ~1.0 M at 7.7 GeV
- Time is approx 1 CPU wk
- Footprint is about 1.75 TB.
Groups:
- jwebb's blog
- Login or register to post comments