Bulletin Board Compression
List of: Discussion Topic
Subjects: History and Roll
Contents: Kernel

If an entity has been modified in several different API_BEGIN / API_END blocks, there will be several bulletins for that entity, each on a different bulletin board.

When the option compress_bb is on (default), at the end of each successful block the bulletins in the bulletin board created for that block are merged with those from the previous bulletin board, so they appear as though the operations occurred in the same block. This should save memory used by extra bulletins and backup copies of modified entities. It should also save time during roll back.

In some cases performance can be improved by setting the compress_bb option off, since the time to compress the bulletin boards can be prohibitive in cases in which a single delta state is used for many API calls.
PDF/KERN/07HIST.PDF
HTM/DATA/KERN/KERN/07HIST/0005.HTM