Re: Memory in systemctl status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Sep 28, 2020 at 10:08:15AM +0200, Reindl Harald wrote:
> Am 27.09.20 um 23:39 schrieb Benjamin Berg:
> >>>> however, that value makes little to no sense and if that's the same
> >>>> value as accounted for "MemoryMax" it's plain wrong
> > But it does make sense. File caches are part of the working set of
> > memory that a process needs. Setting MemoryMax=/MemoryMin=
> > limits/guarantees the size of this working set. These kinds of limits
> > or protections would be a lot less meaningful if caches were not
> > accounted for.
> 
> sorry but that is complete nosense
> 
> caches are freed as soon whatever process asks for RAM and so they are
> *not* part of the working set
> 
> 
> my webserver is killed because it served at monday, tuesday, thursday
> and friday 4 different files with 2 GB?

  Why "killed", you wrote yourself caches are freed. So are they freed
or aren't they?


-- 
Tomasz Torcz               “Never underestimate the bandwidth of a station
tomek@xxxxxxxxxxxxxx        wagon filled with backup tapes.”  — Jim Gray

_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel




[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux