The major difference between the context
buffer and the normal database and table buffers is that it is only refreshed at given intervals. There
is no attempt to update it synchronously, or even nearly synchronously. This means that it is not appropriate to use it for every context or context module.
You can set the maximum number of entries to be buffered. The default is 128. This number only applies to the permanent buffer for a single module. Within a transaction, all of the data that occurs is stored in the buffer unless you have switched off buffering for the module. It is usually best to leave the maximum buffer size set to 128. It is not often that a large number of key combinations occur within one hour on a single application server. Even if this does occur, you can expect combiniations from the first 128 entries to be repeated. The system resets the buffer after one hour, which should ensure that no one module monpolizes it.
The E buffer gives the fastest access, since it can find the values requested in the DEMAND statement in a single step. Under certain circumstances, it can return a smaller number of hits than the I buffer.