- jeromel's home page
- Posts
- 2020
- 2019
- 2018
- 2017
- 2016
- 2015
- December (1)
- November (1)
- October (2)
- September (1)
- July (2)
- June (1)
- March (3)
- February (1)
- January (1)
- 2014
- 2013
- 2012
- 2011
- 2010
- December (2)
- November (1)
- October (4)
- August (3)
- July (3)
- June (2)
- May (1)
- April (4)
- March (1)
- February (1)
- January (2)
- 2009
- December (3)
- October (1)
- September (1)
- July (1)
- June (1)
- April (1)
- March (4)
- February (6)
- January (1)
- 2008
- My blog
- Post new blog entry
- All blogs
HPSS disk cache and Water marking
During Run 14, I looked into the HPSS cache usage and its water marking behavior.
Since a picture is worth 1,000 words, let us look at a large period of time
In short, the upper WaterMark is kicking too early for the 52 TB cache. In average over a large period, the 70% dropped cache occupancy at an average of ~ 15% (could be even lower but the HWM is of interrests). Even at the worst moment, the HWM never went beyond 83% or a 14% dispersion to average at worst.
I would tend to conlude we could increase the HWM from 70% safely to 80%. An absolute dispersion of 14% would still be at a safe 94% while a relative dispersion of 14% would be reaching 93%. Being too conservative (by leaving where it is) instead of the proposed HWM @ 42 TB cleans the cache too often and decrease the opportunity to recover files not yet on tape (6 TB worth).
However, the RCF want to keep the margin in case they do have a maintenance of the back-end tape system requiring hours of downtime (then the extra space would fill up). 6 TB worth at 1.2 Gb/sec is = 9 GB/mnts or 540 GB/hour so a ~ 11.4 hours downtime margin.
- jeromel's blog
- Login or register to post comments