1752292 Members
4524 Online
108786 Solutions
New Discussion

filecache_min max error

 
SOLVED
Go to solution
zxcv
Super Advisor
Solution

Re: filecache_min max error

Hi Duncan / Dennis ,

 

I have resolved the problem.

As you can see that hpvm was ocupying all the memory , i just changed the values startup disable and automatic memory allocation to "0" in /etc/rc.config.d/hpvmconf file .

 

Thanks for your help.

Dave Olker
HPE Pro

Re: filecache_min max error

Which version of 11.31 are you running and which version of HPVM?  My guess is you're running the March 2012 or later Fusion and HPVM v6.1 or later.

 

Dave

I work for HPE

[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo

Re: filecache_min max error

Dennis,

 

> >So you have about 52 GB of memory on this system - 10% would be 5.2 GB, 5% would be 2.6 GB.

>

> Huh?  I see 32GB and 522,455 pages of 64 KB each.

 

I was reading this from the OP's kmeminfo output:

 

>> Physical memory = 522455 31.9g 100%

 

Is that wrong?


I am an HPE Employee
Accept or Kudo
Dave Olker
HPE Pro

Re: filecache_min max error


@Duncan Edmonstone wrote:

I was reading this from the OP's kmeminfo output:

>> Physical memory = 522455 31.9g 100%

Is that wrong?


 

Hi Duncan,

 

The kmeminfo output displays the physical memory in three formats - number of pages, bytes, percent.  Looking at his output:

 

Physical memory usage summary (in page/byte/percent):

Physical memory = 522455 31.9g 100%

 

There are 522455 memory pages, 32GB of RAM in the system.  That being the case, we know that the system is using 64K memory pages (32 * 1024 * 1024) = 33,554,432 bytes / 522,455 pages = 64.  This makes sense on an Integrity VM host because we automatically tune the base_pagesize=64 on systems configured as VM Hosts or VSPs.  

 

My guess is this system is running March 2012 release or newer and Integrity VM v6.1 or newer because at that release we automatically grab 92% of the available memory when HPVM starts and assign it to the HPVM/vPar memory pool.  This is expected behavior that is documented in the Integrity VM/vPars v6.1 Admin Guide.

 

Hope this helps,

 

Dave

 

I work for HPE

[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo

Re: filecache_min max error

hmmm - it would appear I have lost the ability to read! Not sure how I was reading that as 52GB???


I am an HPE Employee
Accept or Kudo
Dennis Handly
Acclaimed Contributor

Re: filecache_min max error

>I was reading this from the OP's kmeminfo output:

 

Yes but it also says:

(in page/byte/percent):

nbpg: 65536 bytes

 

And 32 GB matches the pseudo-swap total.

jody_mckinzie
Occasional Advisor

Re: filecache_min max error

I did it like this:

 

kctune filecache_min=5%

kctune filecache_max=10%

zxcv
Super Advisor

Re: filecache_min max error

Thanks Dave , i always had a doubt as to how the calculation was done.