News for hackers. Stuff that matters.
Re:The Move from Linux to FreeBSD by gerow on Sunday November 16, 2014 @04:03AM (#8613770)
One has to be careful when looking at memory usage to judge these kinds of things, though. Linux has a tendency to use memory unused by applications for its own purposes, because it's not being used anyway and it might as well do something useful with it.

Oftentimes this ends up being something like aggressively caching file data so that it doesn't have to write to disk very often. While this does get labeled as "used" memory, it can very quickly be freed up by the operating system by evicting this cached data back to disk if that memory is needed elsewhere.

This can make Linux appear more memory-hungry, but in actuality a better description might be that Linux is more effectively using the resources at its disposal. I'm not saying that this is what's happening in this case, but it's a possibility.

Re:The Move from Linux to FreeBSD by stevekemp on Sunday November 16, 2014 @04:46AM (#8613827)
Agreed. Compare that with http://www.linuxatemyram.com/
Re:The Move from Linux to FreeBSD by dach90 on Sunday November 16, 2014 @08:27AM (#8614157)
The main thing that matters is when I execute a command it runs fast. and OS is fast... As far as I am concerned os could be sending all my free memory to /dev/null. As long as performance and stability stay up; it can do whatever it wants...
Re:The Move from Linux to FreeBSD by Flow on Sunday November 16, 2014 @04:50AM (#8613833)
You think Linux is alone in acting like that?
Re:The Move from Linux to FreeBSD by andreasvc on Sunday November 16, 2014 @04:56AM (#8613844)
No, but maybe others don't report such memory as used, which seems unfortunate to me.
Re:The Move from Linux to FreeBSD by Flow on Sunday November 16, 2014 @05:16AM (#8613867)
FreeBSD has many labels for how it uses memory. Active, Inactive, Cache etc, to specify the purpose. See this question and answer: http://unix.stackexchange.com/questions/134862/what-do-the-d...
Re:The Move from Linux to FreeBSD by Freaky on Sunday November 16, 2014 @10:33AM (#8614404)
They're less labels for purpose and more labels for lifecycle - data you'd consider "cached" can appear just about anywhere. From what I remember (corrections more than welcome):

Active is fully-fledged in use memory, mapped into one or more processes

Inactive is where Active goes when it's less in-use. Cheap to reactivate, but relatively costly to free: can still be mapped into processes, and may be dirty (modified) and thus require writing to disk before being unmapped and cleared for reuse.

Cached is where lesser used Inactive cached data goes before it dies. More costly to reactivate, but cheap to free: No longer mapped directly into any process, and strictly consists of only clean (unmodified) pages that don't need writing back to disk before clearing.

Wired is pinned-down memory that can't be swapped out. ZFS's data and metadata caches are counted here, since it maintains its own (known as the ARC - Adaptive Replacement Cache, after the algorithm it's based on) instead of just relying on the traditional VM page cache.

Re:The Move from Linux to FreeBSD by Sami_Lehtinen on Sunday November 16, 2014 @08:12AM (#8614130)
At least Windows Servers do. Administrators are often confused about why all memory is being used, when it's used by disk cache. (memory mapped files)
Re:The Move from Linux to FreeBSD by metaobject on Sunday November 16, 2014 @08:50AM (#8614189)
You can use 'free -m' to view the actual amount of memory being used.
Re:The Move from Linux to FreeBSD by dorfsmay on Sunday November 16, 2014 @10:39AM (#8614428)
Or:

    free -h
h for human, so it converts to KiB, MiB or GiB depending on which one is the most suitable.