From: marcov@stack.nl   
      
   On 2004-09-28, Jonas Maebe  wrote:   
   >> even worse, if that memory I think I get is really swap space on disk,   
   >> it turns into even MORE of a performance nightmare like I mentioned   
   >> because I might be writing it to disk multiple times.   
   >   
   > Indeed, so the best strategy is to let the OS handle this and find the   
   > right balance. On *nix-type systems, you do this using memory mapped   
   > files: you more or less say that the "swap" space corresponding to a   
   > particular memory range lies inside an already existing file.   
      
   btw,   
   Windows also has mmap functionality.   
      
   A small last read and read ahead cache in userland can also be useful,   
   just keep it small.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)