Publication Strategies and Performance

performance
8

For this single publication, could you do:

  1. NO_MERGE_NO_HISTORY
  2. Switch the cursor to use polling mode
  3. Set pollingIntervalMs as low as required (this will determine the maximum amount of time the published data could be out-of-date)
  4. Increase/decrease pollingThrottleMs as required (this will make it so that even if a server does a bunch of db updates then that server still won’t immediately republish)
  5. Disable redis oplog for this collection (configured using SomeCollection.configureRedisOplog as shown in the redis oplog docs)

Whether or not this strategy works is dependent on (a) how expensive the polling is and (b) how much latency in the reactivity is acceptable.

Performant way of publishing collection counts in Meteor 3.0 in 2024