https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-830 Lustre <p>lbuild caches kernel and ofed build product. Currently that cache grows without any pruning. lbuild should do a pruning on each run to keep the amount of cache under control.</p> LU-830

need to clean lbuild's reuse cache

Improvement Minor Resolved Cannot Reproduce Brian Murrell Brian Murrell Wed, 9 Nov 2011 11:00:29 +0000 Mon, 29 May 2017 02:45:58 +0000 Mon, 29 May 2017 02:45:58 +0000 Lustre 2.1.0 0 2 <p>Brian, how do you think we should do that?</p> <p><a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=mdiep" class="user-hover" rel="mdiep">mdiep</a>: I don't remember the details of the cache TBH. But cache management is about removing the oldest, least used cache entries. There are tons of algorithms out there for doing so. But before you can even implement one of those you need to know when each item in the cache is used.</p> <p>I have a faint recollection of there being a "last-used" indicator in each cache entry, such as touching a file when it was last used, etc. That at least gets you the oldest-used items. Maybe that is good enough. You just gather up all of those last-used markers and delete the entries that are the oldest.</p> <p>But beware of incorrect algorithms. Algorithms based on time alone are usually wrong. i.e. "delete all entries older than xx days". A cache is at it's most effective when it's full. The only reason to remove entries is to make room for new entries. So an algorithm would be "I need to add a new entry, which is yy size big so I need to remove only enough of the oldest entries to free up yy space".</p> <p>Close old ticket.</p> Development Rank 1|hzw2nb: Rank (Obsolete) 10511 Story Points 3.0