search

koopjs / koop-provider-marklogic

A Koop Provider that can be used to exposed data in MarkLogic via Esri feature services
https://koopjs.github.io/koop-provider-marklogic/
Other
6 stars 11 forks source link

Performance issue in koop featureservice request #179

Closed MayuriSivanesan closed 1 year ago

MayuriSivanesan commented 2 years ago

We have begun load testing of about 100 concurrent users for our koop-provider-marklogic project. With every request the time taken to fetch features from featureserver gradually increases. Some of them taking nearly more than 70secs to complete which affects application's performance. We have around 20000 features in featureservice and querying for about 5000 features at once. There are no errors found in the server log. The time taken to complete each response is shown as graph in the attached image MicrosoftTeams-image (4)

jkerr5 commented 2 years ago

What does the performance look like on the MarkLogic side? Are the requests serviced quickly? I believe the koop logs should should the request times but you can also just look at the meters data on the MarkLogic side.

MayuriSivanesan commented 2 years ago

Please refer attached file for server logs from koop and meters data from marklogic MarkLogic geoQueryService performance.docx

jkerr5 commented 2 years ago

It looks clear that this is a resource limitation on the backend and not an issue with the koop provider so I will close this for now. If it is determined that the provider is a bottleneck of some sort in the future, we can reopen it.