| Summary: | ASTERISK-17996: timing dahdi priority | ||
| Reporter: | Jacob LIpstein (jacobli) | Labels: | |
| Date Opened: | 2011-06-10 12:54:01 | Date Closed: | 2011-06-13 13:35:19 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_timing_dahdi |
| Versions: | 1.8.4 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | OpenSuSE 11.X | Attachments: | |
| Description: | At all of asterisks we are running we were using dahdi timing. But at some point after linux kernel upgrade the timerfd became available and asterisk started using timerfd timing instead dahdi. After timerfd took priority over dahdi we started noticing CPU usage spikes and even asterisk froze completely 1-2 times in a week. It took more than two months for us to figure out what is a root of problem. So I'd suggest to set dahdi .priority (is 100 now) to something higher than 200 (current priority of timerfd timing) in order to force asterisk to use dahdi timing by default (if it is available). I'm pretty sure it affects any asterisk 1.8 version. | ||
| Comments: | By: Leif Madsen (lmadsen) 2011-06-13 13:35:19.951-0500 After speaking with the developers, no change is required here. If there are bugs with res_timing_timerfd, that is not a reason to make it less of a priority. The priority is setup like so because res_timing_dahdi is less efficient than res_timing_timerfd. | ||