| Subject | new Direct I/O for DataBase Files (interbase) - interesting |
|---|---|
| Author | tomc7777777 |
| Post date | 2011-05-12T11:35:11Z |
Does anyone know if there are any plans for this in FB?
http://docs.embarcadero.com/products/interbase/IBXEUpdate2
InterBase Direct I/O for DataBase Files
The direct Input/Output (I/O) capability makes InterBase more scalable with very large databases on systems where there are memory resource limitations. With the Update 2 release, InterBase enables this "direct I/O" functionality on Windows OS. This functionality circumvents the issue observed by many on Windows 2008 R2 and Windows 7 64-bit OS editions where System File Cache uses up too much physical memory leading to sluggish system performance.
Issue: InterBase uses buffered file I/O on all platforms to perform I/O on database pages for the file on disk. The pages are delivered via the System File Cache, which acts as a duplicate store of the pages on RAM. Subsequent loads of the same page(s) will be quickly served by the OS kernel if the page exists in the System File Cache. On systems where there is high contention with other files for the System File Cache (a shared pool used by all processes for buffered file I/O) the performance of InterBase may not be optimal. If available System File Cache is limited due to RAM resource limitations, the kernel must spend time cleaning up unused blocks of memory from other processes as well as provide for servicing a new block I/O request.
http://docs.embarcadero.com/products/interbase/IBXEUpdate2
InterBase Direct I/O for DataBase Files
The direct Input/Output (I/O) capability makes InterBase more scalable with very large databases on systems where there are memory resource limitations. With the Update 2 release, InterBase enables this "direct I/O" functionality on Windows OS. This functionality circumvents the issue observed by many on Windows 2008 R2 and Windows 7 64-bit OS editions where System File Cache uses up too much physical memory leading to sluggish system performance.
Issue: InterBase uses buffered file I/O on all platforms to perform I/O on database pages for the file on disk. The pages are delivered via the System File Cache, which acts as a duplicate store of the pages on RAM. Subsequent loads of the same page(s) will be quickly served by the OS kernel if the page exists in the System File Cache. On systems where there is high contention with other files for the System File Cache (a shared pool used by all processes for buffered file I/O) the performance of InterBase may not be optimal. If available System File Cache is limited due to RAM resource limitations, the kernel must spend time cleaning up unused blocks of memory from other processes as well as provide for servicing a new block I/O request.