The censhare embedded database (CDB) saves resources through compression and fast rebuilding of the index. In addition, find comprehensive statistics to evaluate the data structure.

Introduction

A rebuild of the censhare database (CDB) is now around 50 percent faster than it was before. This is achieved by downsizing the footstep of the indexes by about 50 percent in terms of reduced memory consumption and smaller file sizes. The admin module "Embedded database statistics" has been designed more clearly and provides further information by formatting the output via XML/XSLT.

You can find it in the Tools menu (Gear) in the censhare Admin Client. In addition, there is a separate module for precise analysis of resource requirements of the data called Embedded database data analysis. By the downward sorting order, you can easily isolate the heavyweights in the CDB.

From left to right the column headings refer to:

  • key
  • name of feature
  • total number of indexes
  • total size
  • number of entries in the cache 
  • the memory it occupies (cache size)

The CDB now uses separate caches for temporary and persistent nodes and data. The new feature named "cleaner-max-files-to-evict-per-run" is used to limit the number of items to be released per transaction. All this relieves the cleanup process. With the change to ICU (International Components for Unicode) for the collation keys which are compressed, the size of the CDB may be reduced. The monitoring is more precise because the actual memory footprint is tracked in bytes besides the number of entries in the database. This results in a better overview of the level of utilization of the files. This is calculated exactly. The translation memory uses a separate CDB index to search for exact matches in addition to the regular database for fuzzy search.

Automatic  synchronisation

The automatic synchronization is running every hour. Manual triggering of the sync process is possible and this process is very fast since only asset ID and CCN numbers are compared between the Oracle database and the CDB.

Comprehensive database data analysis

Configuration

Compression of the CDB files is optional, which yields space savings of around 25 percent. The compression level is a configurable value in the censhare Admin Client, in the Embedded Database settings, under cdb-deflater-level.

Default is "0" (without compression).

This can be configured with values between "0" and "9" identical to the degree of compression for RMI-server connections.