-
Bug
-
Resolution: Done
-
Medium
-
London Release
-
None
Summary
We are facing issues with id-searches and searches endpoint's performance when using filters for a public/private attribute.
Response takes anywhere from 5 to 15 minutes
Reproduction
Load 10k CmHandles to NCMP using JMeter and docker compose file.
Execute below queries.
Results
/ncmp/v1/ch/id-searches, no filter (body: {}), response time: 1.3 sec
/ncmp/v1/ch/searches, no filter (body: {}), response time: 1.3 sec
/ncmp/v1/ch/id-searches, response time: 6m 45 sec
request body:
{ "cmHandleQueryParameters": [ { "conditionName": "hasAllProperties", "conditionParameters": [ { "emsId": "7" } ] } ] }
/ncmpInventory/v1/ch/searches, no filter, response time: 1 sec
BTW, at this point no filter request body only works with this one:
{
"cmHandleQueryParameters": []
}
with {}, response is HTTP 500.
With empty body, it's bad request. So it is not the same as the other endpoints.
/ncmpInventory/v1/ch/searches, response time: 14 mins
request body:
{ "cmHandleQueryParameters": [ { "conditionName": "hasAllAdditionalProperties", "conditionParameters": [ { "emsId": "7" } ] } ] }