Auto Allocation API Performance Degrades As The Number Of Ipv6 Subnets In Free State are Matching The Filter
(Doc ID 1448908.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Communications Internet Name and Address Management - Version 6.1.3 and later
Information in this document applies to any platform.
Auto Allocation API (AutomaticAllocation.allocateResources()) performance is fine when the number of IPv6 subnets in free state matching the filter criteria are less. As the number of IPv6 subnets in free state matching the filter criteria increases (above 1000) the performance degrades gradually.
Our test indicate that the when the number of IPv6 subnets in free state matching the filter criteria is up to 500, the response time is ~4secs.
When the number of IPv6 subnets in free state matching the filter criteria is around 1700, the response time is ~14.5secs.
The below query took 6secs. to return the IPv6 subnets in free state matching the filter criteria CUST_V6_NT_56:
[21/Oct/2011:05:12:00 +1100] conn=342 op=4 msgId=5 - RESULT err=0 tag=101 nentries=1714 etime=6
Policy Services took around 5 secs. to choose the best suitable IPv6 subnet out of the list returned, after which the below query was triggered.
[21/Oct/2011:05:12:05 +1100] conn=342 op=5 msgId=6 - RESULT err=0 tag=101 nentries=1 etime=0
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document