Sudden grow of memory in "Laundry" state

[Robert]

Here is one more from another identical machine:

Mem: 1237M Active, 10G Inact, 15G Laundry, 3591M Wired, 846M Free
ARC: 81M Total, 869K MFU, 46M MRU, 32K Anon, 491K Header, 34M Other
      4664K Compressed, 43M Uncompressed, 9.36:1 Ratio
Swap: 32G Total, 1152M Used, 31G Free, 3% Inuse

and one unaffected:

Mem: 392M Active, 9621M Inact, 136K Laundry, 6106M Wired, 15G Free
ARC: 110M Total, 2321K MFU, 54M MRU, 165K Anon, 643K Header, 53M Other
      6252K Compressed, 50M Uncompressed, 8.25:1 Ratio
Swap: 32G Total, 11M Used, 32G Free


All machines are identical and are running same single active process.

There are no memory leaks in the process code (at least not through the 
mmap).

Size of all "Active" allocations is roughly 1.5-2GB on all machines.


On 10/24/18 11:25 AM, Robert wrote:
> Sorry, that wasn't my output, mine (related to the screenshot I've 
> sent earlier) is:
>
> Mem: 1701M Active, 20G Inact, 6225M Laundry, 2625M Wired, 280M Free
> ARC: 116M Total, 6907K MFU, 53M MRU, 544K Anon, 711K Header, 55M Other
>      6207K Compressed, 54M Uncompressed, 8.96:1 Ratio
> Swap: 32G Total, 15G Used, 17G Free, 46% Inuse
>
>
> I'm OK with a low "Free" memory if OS can effectively allocate from 
> "Inactive",
>
> but I'm worrying about a sudden move of a huge piece of memory into 
> "Swap" without any relevant mmap calls.
>
>
> My question is: what else (except mmap) may reduce "Free" memory and 
> increase "Laundry"\"Swap" in the system?
>
> Thanks.
>
>
> On 10/24/18 9:34 AM, Mark Millard wrote:
>> On 2018-Oct-24, at 11:12 AM, Rozhuk Ivan <rozhuk.im at gmail.com> wrote:
>>
>>> On Wed, 24 Oct 2018 10:19:20 -0700
>>> Robert <robert.ayrapetyan at gmail.com> wrote:
>>>
>>>> So the issue is still happening. Please check attached screenshot.
>>>> The green area is "inactive + cached + free".
>>>>
>>>>   . . .
>>> +1
>>> Mem: 845M Active, 19G Inact, 4322M Laundry, 6996M Wired, 1569M Buf, 
>>> 617M Free
>>> Swap: 112G Total, 19M Used, 112G Free
>> Just a limited point based on my understanding of "Buf" in
>> top's display . . .
>>
>> If "cached" means "Buf" in top's output, my understanding of Buf
>> is that it is not a distinct memory area. Instead it totals the
>> buffer space that is spread across multiple states: Active,
>> Inactive, Laundry, and possibly Wired(?).
>>
>> In other words: TotalMemory = Active+Inact+Laundry+Wired+Free.
>> If Buf is added to that then there is double counting of
>> everything included in Buf and the total will be larger
>> than the TotalMemory.
>>
>> Also Inact+Buf+Free may double count some of the Inact space,
>> the space that happens to be inactive buffer space.
>>
>> I may be wrong, but that is my understanding.
>>
>>
>> ===
>> Mark Millard
>> marklmi at yahoo.com
>> ( dsl-only.net went
>> away in early 2018-Mar)
>>