| Networked %SK% |
| Network Contention |
| Directory Exists on Novell |
| QTIPS - String Space Format Errors |
| QTIPS - Postscript Driver Problem |
| QTIPS - String Space Format Errors |
| QTIPS - File Handle Structure |
| Caching in on the Frames Array - Mike Pope |
| What's New (and un(der)documented!) In 2.12 |
| Creating Your Own Background Processes |
| @ATTACK - @Last.Select.Process |
| Reader's Forum |
| QTIPS - Menu Item Pre-Processing |
RevMedia FKB
| Document | V3I7A3 |
| Title | QTIPS - File Handle Structure |
| Keywords | FILE CACHE HANDLE STRUCTURE I/O MODULO |
| Text | Mike Pope of Revelation Technologies reveals the following information courtesy of PT in the RevTech Labs The modulo of the file when it is opened is stored as a part of the file handle (See REVMEDIA Vol 2 Issue 7) in bytes 8 to 13 The modulos of five files are cached locally bytes 2 7 of the handle are a pointer into the cache The cached modulo is updated WITH each record I/O An implication is that file I/O to more than 5 files means cached modulos are discarded more often; on a network the cache may not be maintained at all If the modulo for the CURRENT file isn't in the cache Linear Hash rereads the modulo FROM the file header resulting in extra disk I/O and loss of PERFORMANCE The two points Mike makes FROM this are that 1) file I/O can suffer indirectly by ACCESSING 6 files as part of a single process or on a network and 2) the modulo in the handle isn't used for anything particularly useful (Volume 3 Issue 7 Page 7) |
Page last modified: 08/02/03