Background initialization of observers or other optimizations about meteor-peerdb HOT 2 CLOSED

I was looking over the code to learn how things are done and got a hunch that the initial find (on which observeChanges is called) is behind this delay. That would mean that the number of document records (rather than document classes) affects initialization time, and it does turn out that is the case. On an empty database, enabling observes is practically instantaneous (no matter how many reference fields and other observers you have set up).

So the solution to my problem is to simply develop on a smaller database and am thus closing this ticket as it does not need change in PeerDB. The question still remains, if it is possible to optimize anything for working on large datasets, and one can feel free to reopen this issue if they require it.

from meteor-peerdb.

Related:

• meteor/meteor-feature-requests#88
• meteor/meteor#9862

Yes, there is nothing to be done with what is currently available in Meteor.

from meteor-peerdb.