> Swapping is an important case. But 9 times out of 10 you are managing
> memory in caches, and throwing unused pages into swap. You aren't busily
> paging the data back an forth. But if I have to make a choice in
> what kind of situation I want to take a performance hit, paging
> approaching thrashing or a system whose working set size is well
> within RAM. I'd rather take the hit in the system that is paging.
It means that you prefer system dying under much lighter load. At some
point any box will get into feedback loop, when slowdown from VM load
will make request handling slower, which will make temp. allocations
needed to handle these requests to be kept around for longer periods,
which will contribute to VM load. The question being, at which point
will it happen and how graceful will the degradation be when we get
near that point.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/