Date: Sat, 10 Feb 1996 23:10:58 +0100 (MET) From: Luigi Rizzo <luigi@labinfo.iet.unipi.it> To: terry@lambert.org (Terry Lambert) Cc: hackers@FreeBSD.ORG Subject: Re: Compressed RAM/SWAP Message-ID: <199602102210.XAA05138@labinfo.iet.unipi.it> In-Reply-To: <199602102027.NAA16493@phaeton.artisoft.com> from "Terry Lambert" at Feb 10, 96 01:27:09 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> The "RAM doubler" products are non-products. For BSD, you might be > able to compress swap, but this is not the same thing. > > In general, it is a bad thing to compress swap, because swap contains > only active, dirty pages (BSD is a memory overcommit architecture), > and so it is likely that the swap will be referenced again. > The two caveats on a VM capable system are: > > 1) It reduces the swap utilization in trade for CPU cycles; > on a system where swap dynamically grows (Win95 or > NeXTStep, etc.), this can be a (very very short term) win > in a low-space scenario, where it's impractical or disallowed > to grow the available swap. > > 2) It reduces the swap utilization in trade for CPU cycles: > on a system with a fixed size swap area, this allows you to > overtax the available swap of an overloaded machine to make > it an even more overloaded machine. As all tradeoffs, it might help in some cases. When you have your CPU idle while writing/reading to disk, you might as well use your CPU to compress pages and move them somewhere else, but still in RAM. When your disk is very slow (or it is behind a network IF) this might help as well. I guess this is case #3 in your list. > On the other hand, RAMDoubler sales have been huge. It's probably > sold more volume than "instant water" (a similar product), so who am > I to rain on your parade. 8-). I did not say I would have bought one, just wanted to investigate if there is something good in the idea :) Luigi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602102210.XAA05138>