Scale - Service provisioning -- It is taking 4.5 to 5 hours to configure 1000 services ( l2vpn , L2vpn SRTE , L3vpn , L3vpn with SRTE): Hi,we have TSDN 4.0.0 M6. CW 194, COE 214 , CAT 202 , SH 250 installedNSO LSA setup: 1 CFS with 2 RFS.we have 60 devices topology.working on Uni-d Scale tetsing for SH. we are in progress of creating 12k services across 48 devices. 31 devices in RFS-1 and 29 devices in RFS-2.we create the services sequentially one by one . as per the wiki, we have configured the commit-queue disabled in RFS.we had a debug session with Priyanka shanrma and as per the suggesion we had ncs config with Rollback false.we have tried as per Priyanka's suggestion to try with enabling commit-queue in RFS. in NSO RFS, with commit-queue enabled , it is taking 2 to 3 seconds to configuring one service.. but while provisioning multiple services next by next, keeping asusual delay of 3 sec is failing to configure the Services with error that another commit in progress in devices.so, obviously we have to increase the delay to a number where it has to finish the commit in devices. So, again, it ended up into the same time now. Hence I have modified the setting back to commit-queue disabled.After reducing the delay to 3 secs delay interval between the service creation, with single user, having commit-quete disabled, it was 4.5 hours to configure 1000 services. Thanks,Arun.M.G
Missed to add few details in the description.Actually, it is taking average of 15 seconds to configure a single service. and we have a delay interval with 3 sec between the service creations.so, in one min , it is 3 to 4 services.In 60 mins, it is average of 180 to 240 services.So, to configure 1000 services, it take 4.5 to 5 hours.Hi Arun ,I talked to Solution test team and here scale results : For CNC 3.0 scale for l2nm service for single service it was 26 sec .In your lab CNC 4.0 we see close to 20 sec per service.As discussed earlier what you see is expected.If you want to reach higher numbers as suggested before, please do scale tests in batches .For example, 25 services then some wait time or plan to be up then next set of services .Thanks,Priyanka