[LU-16757] Allow max_cached_mb to be set as a percentage of system ram

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 2.15.2
• Type: Improvement
• Priority: Minor
• Reporter: James Beal
• Assignee: Patrick Farrell
• Resolution: Duplicate
• Labels: lug23dd

Description

When lustre clients have differing amounts of memory then setting the max_cached_mb  to an absolute number which is the same on all nodes is not likely to provide optimum results. Given vendors like to set this value and place it in the configuration log then allowing max_cached_mb to be a percentage and having the client caculate the exact value to use would be a useability win.

 

We currently do this at Sanger using a ansible templated tuning script:

 

 

{% if adjust_lustre_cache %} {% for key, value in lustre_cache.items() %}

echo We will set the lustre filesystem cache for {{ key }} to {{  (ansible_memtotal_mb * value / 100 )| int }}
lctl set_param llite.{{key*.max_cached_mb={{  (ansible_memtotal_mb * value / 100 )| int }} || true

{% endfor %} {% endif %}

Issue Links

• duplicates: LU-17030 allow setting max_cached_mb with %

Comments

[Tommi Tervo]

Hi,

Looks like PAF fixed this:

https://jira.whamcloud.com/browse/LU-17030

[Peter Jones]

Patrick do you agree that this is a duplicate of LU-17030?

[Patrick Farrell]

Yes, I agree - Or perhaps the other way around, I didn't notice this one when I opened LU-17030.  But yes, LU-17030 fixes this.