View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002137 | SymmetricDS | Bug | public | 2015-01-15 05:53 | 2019-04-23 16:43 |
| Reporter | brickman | Assigned To | |||
| Priority | normal | ||||
| Status | new | Resolution | open | ||
| Product Version | 3.5.17 | ||||
| Summary | 0002137: Database performance degradation with large SYM_DATA | ||||
| Description | Our setup is SymmetricDS 3.5.17 running against a Firebird 2.5.3 Super Classic database. We have 0000946:0000100 nodes connected. As the number of SYM_DATA records increase we observe degradation in the database CPU utilisation. The increase was due to some nodes being offline for several days. We found we could significantly improve performance if we added the following descending indexes (the syntax is Firebird): CREATE DESCENDING INDEX IDX_SYM_DATA_ID_DESC ON SYM_DATA(DATA_ID); CREATE DESCENDING INDEX IDX_SYM_DE_BATCHID_DESC ON SYM_DATA_EVENT(BATCH_ID); CREATE DESCENDING INDEX IDX_SYM_OB_ID_DESC on SYM_OUTGOING_BATCH(BATCH_ID); We initially had problems with SymmetricDS dropping these indexes on startup. We since worked around this by setting "auto.config.database" to false. We also found that the symmetric-schema.xml config does not support descending indexes. Is it possible to explore adding these indexes? | ||||
| Tags | ddl/schema, dialect: firebird, performance | ||||