Summary: | ASTERISK-22488: CDR performance bottleneck | ||||
Reporter: | Richard Mudgett (rmudgett) | Labels: | |||
Date Opened: | 2013-09-09 14:33:32 | Date Closed: | 2013-09-24 13:03:01 | ||
Priority: | Major | Regression? | Yes | ||
Status: | Closed/Complete | Components: | CDR/General | ||
Versions: | SVN | Frequency of Occurrence | Constant | ||
Related Issues: |
| ||||
Environment: | Attachments: | ||||
Description: | Repeatedly doing a local channel chain of 300 eventually causes the system to be bogged down doing CDR processing.
It would appear that create_candidates_for_bridge() needs to be improved since the number of buckets in the the active_cdrs_by_channel container was increased. | ||||
Comments: | By: Richard Mudgett (rmudgett) 2013-09-09 14:35:29.037-0500 See ASTERISK-22482 for local channel chain creation. By: Matt Jordan (mjordan) 2013-09-12 18:58:12.296-0500 Creating the candidates from the channels in the bridge could certainly be done more efficiently. This really needs a two pass look-up: One to get the channels that are in the bridge, the next to get their CDRs from the existing container. That really should prevent the O(n) iteration that occurs currently. |