|
|
|
|||||||
|
|
||||||||
|
|
|
|
|
|||||
| Home | ||||||||
| Free Downloads | ||||||||
| Product FAQs (NT) | ||||||||
| Product FAQs (OpenVMS) | ||||||||
| Product Alerts | ||||||||
| Technical References | ||||||||
| Links | ||||||||
|
||||||||
|
How do I/O Express caching and pool extension affect RMS caches?RMS and I/O Express use two completely different caches. I/O Express non-paged pool extension has no effect on RMS cache. The RMS cache uses paged pool to cache bit maps, file headers and other directory structures. I/O Express uses non-paged pool for data structures, which point to pages in the cache. The Free Page List (FPL) is where I/O Express creates its cache. Pages from the FPL are taken and released, depending on the needs of the system. If many pages are available, then I/O Express will use most of them for the cache. If the FPL is very small, then I/O Express will not use any more for the cache, but will trim its own cache by releasing pages in the cache back to the FPL to keep the system from having to work so hard to locate memory.
If this FAQ helped, please let us know. If you didn't find the answer to your question here please e-mail
|
||||||||
|
|
Executive Software Europe |
|
||||||