<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Jim, I'm forwarding this to lustre-discuss to get a broader community input. I'm sure somebody has some experience with this.<br><div><br><div>Begin forwarded message:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font>I am looking for information on how Lustre assigns and holds pages on client nodes across jobs. The motivation is that we want to make "huge" pages available to users. We have found that it is almost impossible to allocate very many "huge" pages since Lustre holds scattered small pages across jobs. In fact, typically about 1/3 of compute node memory can be allocated as huge pages.<br><br>We have done quite a lot of performance studies which show that a substantial percentage of jobs on Ranger have TLB misses as a major performance bottleneck. We estimate we might recover as much as an additional 5%-10% throughput if users could use huge pages.<br><br>Therefore we would like to find a way to minimize the client memory which Lustre holds across jobs.<br><br>Have you had anyone else mention this situation to you?<br><br>Regards,<br><br>Jim Browne<br><br><br></div></blockquote></div><br></body></html>