Closed baszoetekouw closed 9 years ago
Can you verify this against the "4th set"? Would be interesting to know if the changes in 1.20 contributed to solving or mitigating this memory hog problem.
Ah, seems to work ok on the fourth set! It's quite slow though, but that's to be expected, I guess.
So it will likely be better after the deploy of janus 1.20.2 today, and even further addressed when 1.20.3 makes it to production.
Yesterday, this worked just fine:
to fetch all entities from Janus. Today, I get only a 500 http error :(
The error log is enlightening:
I'm not sure what all 134MB of memory is used for, but all (~1000) entities should easily fit.
Note that fetching of individual entities, either by eid or by entityid, works fine. Therefore, this is not very urgent, I guess.