On Thu, Dec 20, 2018 at 2:35 PM aaronb via golang-nuts
wrote:
>
> Thanks for the clarification. The system I am testing on is swapless, so
> maybe would explain why RSS is not increasing.
>>
>> On a swapless system, freeing pages in a given range happens instantly,
>> regardless of memory pressu
Thanks for the clarification. The system I am testing on is swapless, so
maybe would explain why RSS is not increasing.
> On a swapless system, freeing pages in a given range happens instantly,
> regardless of memory pressure.
>
My suggestion for wording would to be more specific about the de
On Thu, Dec 20, 2018 at 2:13 PM wrote:
>
> The wording is kinda bad. All it means is that the runtime was updated to use
> MADV_FREE instead of MADV_DONTNEED if possible.
>
> You can read about the difference on the madvise(2) man page, but basically
> MADV_FREE is more lazy. There is no actual
The wording is kinda bad. All it means is that the runtime was updated to
use MADV_FREE instead of MADV_DONTNEED if possible.
You can read about the difference on the madvise(2) man page, but basically
MADV_FREE is more lazy. There is no actual impact other than the RSS value
being not as accur
I'm trying out a build of my code under go1.12beta1 and resident memory
usage is not too dramatically different than under go1.11. The wording on
this release note made me think the runtime was going to continually gobble
up memory and not release any until the system had nearly run out, but tha
