To provide fast access to disk resident data (with minimal disk read operations). Synchronization of concurrent database access is implemented in GigaBASEīy means of atomic instructions, adding almost High speed of queryĮxecution is provided by elimination of data transfer overhead and GigaBASE is most efficient for applications fetching records using indices orĭirect object references. Transaction performed by remote node which certainly has negative effect on performance. GigaBASE also supports multiclient modeīased on file system locks, but in this case page pool has to be cleared after each Multiple threads working with the database). Unlike FastDB, which holds all data in memory which can be efficiently sharedīetween multiple processes, GigaBASE page pool is private to the processĪnd so only one process can access the database file (but there can be That is why GigaBASE is able to handleĭatabases which size exceeds size of computers virtual memory.Īs FastDB, GigaBASE provides a very convenient and efficient C++ interface. Interface as FastDB main memory DBMS, but using a page pool instead of GigaBASE is object-relational database system with the same programming Sharing of classes between different databases.Reducing initial size of the database file.Delayed transactions and online backup scheduler.GigaBASE Object-Relational database system
0 Comments
Leave a Reply. |