1 comment:
Patchset:
I agree. Some things which would still keep this feature useful to us but will reduce the performance impact:
1) reduce granularity from 0.1s to 1s: While I'd like to keep 100ms resolution, maybe there's no way to do it efficiently.
2) only start timers and track stats on TCH lchans: We're primarily using this to gather Erlang stats and secondarily to glance site health. Even if it's only TCH it still serves that purpose.
The biggest BSC we're talking about has 4480 SDCCH lchans defined and 3200 TCH. The combination of 1 and 2 above gives us a full order of magnitude drop and then cuts that in half. Maybe a better starting point?
To view, visit change 27081. To unsubscribe, or for help writing mail filters, visit settings.