Reader/Writer lock support has been added, greatly improving performance with large numbers of clients. Reader/Writer locks are more efficient than a standard mutex by avoiding contention when there are many readers. The server mutex over the memory file hash lists has been changed to use a reader/writer lock when this support is enabled at compile time.
c-treeACE has a generic reader/writer lock implementation available for all platforms. On Windows and Solaris systems, native reader/writer lock synchronization objects are used. When c-treeACE starts, it checks if the system supports reader/writer lock functions and, if so, uses them. If not, it uses generic c-treeACE reader/writer lock functions.
The configuration option COMPATIBILITY CTREE_RWLOCK can be used to force c-treeACE to use its reader/writer lock support instead of the native operating system reader/writer lock support.
Look for one of the following messages in CTSTATUS.FCS to indicate which, if any, reader/writer lock support is enabled:
c-tree reader/writer lock support enabled (keyword specified)
c-tree reader/writer lock support enabled (no O/S support)
Windows native reader/writer lock support enabled
See Also