Given I’m a lazy administrator and create an incredibly large incoming call DID range instead of listing the DIDs I’ve actually bought.
When I list available DID’s in my context
Then confd consumes way too much memory and the filtering in very slow.
This is what typically happens in France. The context is created with the following range. 33100000000 to 33999999999.
This range include 900M - 1 possibilities.
I’ve modified the algorithm used to compute the available ranges when considering the DIDs that are already in use and have been able to reduce the memory usage but the slow search is still a problem since the search looks at all extensions containing a given sequence of digits at any position.
I’ve tested limiting the size of ranges to 10k possibilities and it fixes the speed and memory problem.
The fix would need to include a migration that breaks this huge range into smaller ranges based on the currently configured incoming calls.
Given I’m a lazy administrator and create an incredibly large incoming call DID range instead of listing the DIDs I’ve actually bought.
When I list available DID’s in my context
Then confd consumes way too much memory and the filtering in very slow.
This is what typically happens in France. The context is created with the following range.
33100000000 to 33999999999.
This range include 900M - 1 possibilities.
I’ve modified the algorithm used to compute the available ranges when considering the DIDs that are already in use and have been able to reduce the memory usage but the slow search is still a problem since the search looks at all extensions containing a given sequence of digits at any position.
I’ve tested limiting the size of ranges to 10k possibilities and it fixes the speed and memory problem.
The fix would need to include a migration that breaks this huge range into smaller ranges based on the currently configured incoming calls.