[LU-4238] Request for client parameter to limit caching of Lustre files to no larger than a certain size Created: 08/Nov/13 Updated: 15/Sep/23 Resolved: 15/Sep/23 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor |
| Reporter: | Brett Lee (Inactive) | Assignee: | WC Triage |
| Resolution: | Low Priority | Votes: | 0 |
| Labels: | None | ||
| Rank (Obsolete): | 11535 |
| Description |
|
Use case: Clients performing buffered IO in a mixed (small and large files) workload. Goal is to increase performance by keeping the small files in cache. Justification: Ability to avoid caching of large files should keep small files in cache, thereby increasing performance. Implementation: Thinking that a parameter, like the obdfilter.*.readcache_max_filesize parameter on an OSS, could be used. |
| Comments |
| Comment by Robert Read (Inactive) [ 09/Nov/13 ] |
|
The caching on the client side is done by the Linux pageacache and is not done directly by Lustre. However, Lustre might be able to place pages on the end (or the beginning) of the LRU queue so they would be reclaimed immediately. Applications can also do this themselves by using the fadvise() syscall when they open a file. |