I’ve seen this many times with Meteor
Likely related to this: Memory Utilization is running high but it happens for CPU as well.
In summary:
- Never ever use observe/observeChanges in your code. (Imo this should be banned from the Meteor docs and not be publicly available)
- Avoid publishing data, only publish ids, and grab results with a method
- Implement https://montiapm.com/ and have a look at what else is creating observers. Could be some package
and you should be fine.
(in other words, avoid using the Meteor ‘black magic’)