# Query endpoint optimisation

**URL:** <https://community.stardog.com/t/query-endpoint-optimisation/2571>\
**Category:** Support\
**Created:** [July 8, 2020, 11:03am UTC](https://community.stardog.com/t/query-endpoint-optimisation/2571 "2020-07-08T11:03:35Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![bsteenwi](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/bsteenwi/32/654_2.png) [@bsteenwi](https://community.stardog.com/u/bsteenwi)\
**Post date:** [July 8, 2020, 2:31pm UTC](https://community.stardog.com/t/query-endpoint-optimisation/2571/4 "2020-07-08T14:31:07Z")

</div>

Hi again,

If found the problem of the above described behaviour, and it has nothing to do with Stardog.  
The program which iterates over the different ind's had a memory leak.  
And (bad practices) I was running the Stardog database on the same cluster as this program.

So the total memory was getting critical (which resulted in Stardog providing such logs).

Fixed the leak, and ran Stardog on a different node solved the problem.

Kind regards,  
Bram

---

_[View the full topic](https://community.stardog.com/t/query-endpoint-optimisation/2571)._