Meteor perfomance issues with collection observeChanges

performance
21

Thanks for the suggestions, I don’t remember right now where exactly the problem was on our code, but we had to perform a workaround. It was really hard to identify where the original issue was. There was certainly a cascade effect per what we could see in kadira.

After some changes the problem stopped appearing, going to close this topic. Thanks everyone for your input and help!

ps: I think I can’t actually close it haha

22

@diaconutheodor Interesting. Can you elaborate on this point?

23

I have no idea what I meant by that. Maybe the fact that oplog hits you with the data in full? It’s been a year but I don’t exclude the possibility of being wrong.

1 Like
24

Maybe you were referencing the fact that calling observe/observeChanges loads the entire result set of the query into memory?

1 Like