Details
-
Type:
Bug
-
Status:
Ready for QA
(View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: FN
-
Labels:None Labels
-
Customer:OMAN-Tel
Description
updateOldResourcesStatus has performance issue
4s in new 1.5s in old
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.api.nep.mobinets.com/">
<soapenv:Header/>
<soapenv:Body>
<ser:updateOldResourcesStatus>
<!-Optional:->
<subscriberNo>25796019</subscriberNo>
<!-Optional:->
<status>spare</status>
</ser:updateOldResourcesStatus>
</soapenv:Body>
</soapenv:Envelope>
changed the logic of finding ospconnection related to fn_service_trail_hop (FnInternalService.getOspConnection (TransferredOspConnection)) .
we have change the logic of this method (create two new methods in same class with same name and different params) .
instead of for each hop retrieve node1+node2 + retrieving all ospconnections by node1id and node2id then for each connection get the transferred object and check if port1key = port2key (we may have hundreds connections between two nodes) ==> fetching the related node1 + node2 (By nodeName and nodeType) and port1 + port2 (By NeId and portKey) then fetch directly the related ospconnection (only one match)