×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hello Jim,
Am 22.08.2024 um 18:10 schrieb Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>:
To answer the original post, this allows the OP to manage how much memory is used for I/O on each hosted environment, within the hosting system.
Yeah. But since the guest LPAR also has memory being used as cache, and bringing the data as close to the where it is processed eventually should be beneficial, yes?
My intended question was: Is this partitioning of memory into pools (on the hosting side) still relevant, while very modern nowadays machines are equipped with memory in large amounts, and running from extremely performant NVMe?
I manage several systems using these techniques and I would argue they are the current professional standard for anything but the smallest system.
Did you configure these so because you *think* it should be done for the reasons you outlined? Or did you take actual measurements to prove that your thinking had positive effects at all? Or possibly learn that the difference is negligible — something I assume for now with my limited experience with large systems enduring considerable workload?
Again, no offense intended. I'm just curious and want to understand.
:wq! PoC
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
