| Summary |
0004219: Routing should use transaction and batch mode to insert multiple sym_outgoing_batch rows |
|
| Revision |
2019-12-31 15:29 by elong |
|
| Description |
Potential bottleneck in routing when it commits after each sym_outgoing_batch row. Instead, it should use a transaction to insert all rows and then commit. Performance is noticeable when using a thousand nodes with default routing. Also, add separate statistics for inserts and updates to sym_outgoing_batch that are logged during a long run. NOTE: In the future, we could consider using JDBC batch mode as well. |
|
| Revision |
2019-12-31 20:20 by elong |
|
| Description |
Potential bottleneck in routing when it commits after each sym_outgoing_batch row. Instead, it should use a transaction and batch mode JDBC to insert all rows and then commit. Performance is noticeable when using a thousand nodes with default routing. Also, add separate statistics for inserts and updates to sym_outgoing_batch that are logged during a long run. Add separate parameter for flush size of sym_outgoing_batch versus sym_data_event. |