Product Documentation

c-treeACE V11.0 Update Guide

Previous Topic

Next Topic

Deferred File and Index Maintenance

Deferred file and index maintenance postpones certain index and data maintenance operations to background processes, thus offloading performance bottlenecks in various use cases. For example, index update operations can be deferred.

Several very exciting new performance-based indexing features are available with respect to deferred data and index handling.

  • A new deferred indexing feature allows background processing of new index entries for much faster application response times. For data files with many non-critical indexes, this can bring a big boost in performance when large numbers of new keys are added. Bulk load processes can benefit as essential, primary indexes are immediately available, while non-critical indexes are eventually brought to full consistency.

    In addition, new deferred key loading modes are available for permanent index creation allowing deferred loading of key values, such that your index is immediately available, although in an “eventually consistent” state until all keys are completely loaded. At that time, the index switches into a fully available and consistent mode, unless also marked with the above permanent deferred mode.

  • Record Update Callback Functions (Asynchronous Record Update Notifications, Record Update Callback) give essential control to call detailed user-defined actions when a record is modified. Much as a notification event, these events handle any record-update operations and are deferred to a background process for handling. For example, an external indexing process can be called to process data in parallel for non-typical data types.

This precise control remains the hallmark of FairCom’s dedication to the database development community.

Deferred Indexing

TOCIndex