|
|
|
FairCom DB V10 introduced numerous performance gains and tightened security measures. To take a advantage of the power-packed release, you will need to be sure your system is configured correctly. Other options have either been deprecated or changed in behavior.
Customers moving from prior releases should consider the following options and changes in configuring their servers.
Performance
Shared Memory on Unix Systems
V10 and later releases now support shared memory for localhost application connections. Enabling this should give a major performance boost for those applications. The following keyword enables this feature:
COMM_PROTOCOL FSHAREMM
Memory Suballocation Subsystem
There is a configuration for our memory suballocator lists. We strongly recommend testing with this option for performance comparison. Set this value to the number of CPUs available to the FairCom DB process for optimal advantage.
MEMORY_HASH <N>
Data Integrity
Enhanced Automatic Recovery
The RECOVER_DETAILS setting is now default. This option can be removed from previous configuration files.
LOGIDX Improves Recovery
In V10, a mode called LOGIDX is now enabled by default. This potentially adds slightly more overhead than you had in prior versions. However, the payoff is great during recovery. We recommend leaving this default in place.
RECOVER_MEMLOG Speeds Recovery Times
We also recommend adding the RECOVER_MEMLOG option to your configuration. It can greatly speed recovery times and has no effect during normal operation.
Access Security
Encrypted User/Group Information
ADMIN_ENCRYPT YES is the default in V10 and later. By default, this option scrambles the user group information file FAIRCOM.FCS using FairCom's CAMO technology. (CAMO or "Camouflage" is an older, legacy method of hiding data, which is not a standards-conforming encryption scheme, such as AES. It is not intended as a replacement for Advanced Encryption or other security systems.) AES encryption is available if ADVANCED_ENCRYPTION YES is specified in ctsrvr.cfg.
To disable this encryption level, add ADMIN_ENCRYPT NO to your configuration file.
Guest Logons Denied
Guest logons (logons without any provided user name) are now denied by default. To enable applications that don't use FairCom DB user authentication you now need to explicitly allow those connections.
GUEST_LOGON YES
Compatibility
Transaction Log Writing
The COMPATIBILITY SYNC_LOG setting is now deprecated. Use COMPATIBILITY LOG_WRITETHRU (which has exactly the same behavior).
Commit Read Locks
Commit read locks prevent dirty record reads during the commit phase of a transaction.
COMPATIBILITY COMMIT_READ_LOCK is now default. You can remove this option from previous configuration files if used (introduced in V9).
Caching: TDATA_WRITETHRU vs. UNBUFFERED_IO
TDATA_WRITETHRU uses the file system cache. The file is placed into a mode that causes the write to go to file system cache and then to disk before returning; the data still resides in file system cache.
UNBUFFERED_IO completely bypasses the file system cache.
