[TSDR-19] Performance Issue with Cassandra Persistence Created: 30/Jan/16 Updated: 03/Feb/16 Resolved: 03/Feb/16 |
|
| Status: | Resolved |
| Project: | tsdr |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Sharon Aicler | Assignee: | Sharon Aicler |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 5152 |
| Description |
|
While checking for scale I notice a major issue with Cassandra performance persisting records. Looking into the code I notice that it is persisting records one by one instead of using a batch. Tests has shown that with 127 switches the persistence time is between 50 and 60 seconds for 100K records. With batching it is down to 5-6 seconds. |