From: marcov@stack.nl   
      
   On 2004-09-30, VBDis  wrote:   
   > Im Artikel , Marco van de Voort   
   > schreibt:   
   >   
   >>> OK, define a "Windows-minded memory grab" then.   
   >>   
   >>Depends on what your program exactly does. If you e.g. only precache some   
   >>file, it is easier to e.g. use a memorymapping call. That way, the OS will   
   >>do your caching, and that will probably be a lot better.   
   >   
   > That's a good suggestion, with some limitation on huge files. The view of   
   every   
   > mapped file reduces the virtual address space of the application, so that it   
   > may be impossible to map multiple files entirely at the same time. For   
   partial   
   > mappings of files the usual considerations apply to the size of the memory   
   > buffer...   
      
   True, but for a former dos app, it is unlikely that the vm-space will be   
   exhausted soon :-)   
      
   > When the files fit into the logical address space, regardless of RAM size,   
   > memory mapped files are both fast and easy to use. For huge files I'd go with   
   > Laura's suggestion, sequential reads of records can be amazingly fast.   
      
   For huge files I'd go for FPC/AMD64 ;-)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)