WAS v8.5 > Tune performance > Tune Service integration > Tune messaging engine data stores > Increasing the number of data store tables to relieve concurrency bottleneck

Increasing the number of item tables for a messaging engine when tables are not automatically created

If a concurrency bottleneck occurs on the item tables, increasing the number of item tables will increase the throughput of the messaging engine.

Before performing this task ensure the messaging engine is using a data store, and that its Create tables option is set to False.

1. Relevant performance monitoring tools show the throughput of a messaging engine is inefficient.

2. Use the database performance monitoring tools to examine lock statistics for the item tables for evidence of a bottleneck. Consult database documentation on how to interpret the locking statistics.

3. Create tables and increase data store attributes.

   • Create tables for the data store schema. For more information see Create data store tables

   • Increase number of permanent tables or temporary tables, or both, for the data store. For more information see Configure a messaging engine data store to use a data source

   We can only increase the number of permanent tables or temporary tables, not decrease them.

4. Stop and restart the WAS so that configuration changes take effect. The extra tables are used when the messaging engine restarts.
5. Observe the effect on throughput and lock statistics by checking performance monitoring tools. Consider whether any improvement is sufficient and modifying the data store attributes further would be beneficial

Related

Generate the DDL statements needed to create or alter data store tables

Reference:

Data store tables

+

Search Tips   |   Advanced Search