On 8/17/12 7:15 AM, Marie Bacuno II wrote:
On Aug 16, 2012, at 18:47, Garrett Cooper wrote:
On Thu, Aug 16, 2012 at 6:44 PM, Garrett Cooper wrote:
On Thu, Aug 16, 2012 at 5:46 PM, Gezeala M. Bacuño II wrote:
Hello fellow listers,
On a server with 512GB RAM it appears that vm.kmem_size_ma
On Aug 16, 2012, at 18:47, Garrett Cooper wrote:
> On Thu, Aug 16, 2012 at 6:44 PM, Garrett Cooper wrote:
>> On Thu, Aug 16, 2012 at 5:46 PM, Gezeala M. Bacuño II
>> wrote:
>>> Hello fellow listers,
>>>
>>> On a server with 512GB RAM it appears that vm.kmem_size_max is not
>>> being auto-tun
On Thu, Aug 16, 2012 at 6:44 PM, Garrett Cooper wrote:
> On Thu, Aug 16, 2012 at 5:46 PM, Gezeala M. Bacuño II
> wrote:
>> Hello fellow listers,
>>
>> On a server with 512GB RAM it appears that vm.kmem_size_max is not
>> being auto-tuned to use >329853485875 (~307GB).
>>
>> On this machine vm.km
On Thu, Aug 16, 2012 at 5:46 PM, Gezeala M. Bacuño II wrote:
> Hello fellow listers,
>
> On a server with 512GB RAM it appears that vm.kmem_size_max is not
> being auto-tuned to use >329853485875 (~307GB).
>
> On this machine vm.kmem_size is equal to vm.kmem_size_max
>
> # from sysctl
> vm.kmem_si
Hello fellow listers,
On a server with 512GB RAM it appears that vm.kmem_size_max is not
being auto-tuned to use >329853485875 (~307GB).
On this machine vm.kmem_size is equal to vm.kmem_size_max
# from sysctl
vm.kmem_size_max: 329853485875
vm.kmem_size: 329853485875
On a machine with 1GB of RAM