第3章 存储与文件结构.pptVIP

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Hardware Swizzling Page with short page identifier 2395 was allocated address 5001. Observe change in pointers and translation table. Page with short page identifier 4867 has been allocated address 4867. No change in pointer and translation table. Page image after swizzling Hardware Swizzling After swizzling, all short page identifiers point to virtual memory addresses allocated for the corresponding pages functions accessing the objects are not even aware that it has persistent pointers, and do not need to be changed in any way! can reuse existing code and libraries that use in-memory pointers After this, the pointer dereference that triggered the swizzling can continue Hardware Swizzling Optimizations: If all pages are allocated the same address as in the short page identifier, no changes required in the page! No need for deswizzling ： swizzled page can be saved as-is to disk A set of pages (segment) can share one translation table Pages can still be swizzled as and when fetched (old copy of translation table is needed) A process should not access more pages than size of virtual memory ： reuse of virtual memory addresses for other pages is expensive Disk versus Memory Structure of Objects The format in which objects are stored in memory may be different from the format in which they are stored on disk in the database. Reasons are: software swizzling – structure of persistent and in-memory pointers are different database accessible from different machines with different data representations Make the physical representation of objects in the database independent of the machine and the compiler Can transparently convert from disk representation to form required on the specific machine, language, and compiler, when the object (or page) is brought into memory Large Objects Large objects : binary large objects (blobs) and character large objects (clobs) Examples include: text