Go to the first, previous, next, last section, table of contents.


Global database options

This window is used for setting of parameters related to the message database.

Buffers
This value defines the number of buffers the buffering system uses. Note that 13 is the default number of buffers and you will not notice any significant speed difference by increasing this number, although reading and parsing messages in reference mode is slightly faster with a higher setting. The Buffer size has much greater influence on performance.
Buffer Size
This value is the size of each buffer. Default is 5096, and should not be any less (since this is the size of one of the hash-tables.) However, if you have the memory to spare, you should increase this for higher performance. These buffers are used by BBSRead.library and will be freed when bbsread.library is flushed out of memory or after a 5 minutes timeout if the library is not in use anymore.. Defining too large buffer here might make THOR slower because of overhead. Usually, 20000 is a good size of the buffer.
Msgs to Keep
This value is used when packing conferences. If the number is set to e.g. 100, all messages except for the newest 100 will be deleted when you pack messages This is the default for all conferences if nothing else is defined in the section Conference Configuration. If you set the checkbox gadget to "Ignore", no messages will be packed with this parameter.
Days to Keep
This value is used when packing conferences, unless another value is defined in the section Conference Configuration. When packing, all messages older than this number of days will be removed. This works seemless together with the Msgs to Keep value. If you set the checkbox gadget to "Ignore", no messages will be packed with this parameter.
Xpk Method
This is the Xpk method that will be used when packing messages, e.g. "NUKE" or "RAKE".
Auto Xpk Packing
If this gadget is checked, Xpk packing will be preformed when the messages are imported into the database. Otherwise, if will only happen when packing messages.
Haze Levels
This feature is named after Dave 'hazy' Haynie. On emphasize/kills, any matching message can be given a special Haze Level . The various haze-levels are defined in the Global Configuration in ConfigTHOR and defines the minimum number of days the message is to remain in the messages database before it can be purged. Tip: If you want to keep your own messages (the ones you write yourself) in the database somewhat longer, setup a Mark Unread trigger on your own email address, then set a haze level that'll keep the message in the database longer than other messages.


Go to the first, previous, next, last section, table of contents.