Increasing the number of data store tables to relieve concurrency bottleneck
Service integration technologies enables users to spread the data store for a messaging engine across several tables. In typical use this is unlikely to have a significant influence. However, if statistics suggest a concurrency bottleneck on the SIBnnn tables for a data store, you might try to solve the problem by increasing the number of tables.
About this task
For more information about the set of tables in a data store see Data store tables.
Data | Description |
---|---|
SIB000 | contains information about the structure of the data in the
other two tables - the stream table |
SIB001 | contains persistent objects - the permanent item table |
SIB002 | contains nonpersistent objects that have been saved to the
data store to reduce the messaging engine memory requirement - the temporary item table |
Having multiple tables means you can relieve any performance bottleneck you might have in your system. You can modify SIBnnn tables of the data store of a messaging engine. You can increase the number of permanent and temporary tables (SIB001 and SIB002), although there is no way to increase the number of stream tables (SIB000).
Example
This example illustrates what the SIBnnn tables for a data store might look like after modification:
Data | Description |
---|---|
SIB000 | contains information about the structure of the data in the
other two tables - the stream table |
SIB001 | contains persistent objects - the permanent item table |
SIB002 | contains persistent objects - the permanent item table |
SIB003 | contains persistent objects - the permanent item table |
SIB004 | contains nonpersistent objects that have been saved to the
data store to reduce the messaging engine memory requirement - the temporary item table |
SIB005 | contains nonpersistent objects that have been saved to the
data store to reduce the messaging engine memory requirement - the temporary item table |