subs-manager | Subscriptions Manager for Meteor | Notification library

Depending on the way your app is designed, data-wise, there can be several reasons for this lack of performance.

A few suggestions:

• check that you have indexes in your collections
• avoid doing aggregation in the publication process, i.e. denormalize the db, publish array of cursors instead, limit the size of the documents, etc.
• filter the useless fields in the query
• limit the amount of data to the relevant part (lazy load & paginated subscribe)
• consider global pubs/subs for the collections you use a lot, instead of reloading them too often on a route based pattern
• track small component based subs and try to put them at a higher level to avoid making for instance 30 subs instead of one

My best guess is that you probably need a mix of rationalizing the db "structure" and avoid the data aggregation as much as you can.

You may also have a misuse of the low level collection api (e.g. cursor.observe() stuff) somewhere.