Oleksandr Chekhovskyi 565fa39037 Catch up to oplog at most once per write fence ...

Before this change, number of catch-up attempts was N*M, where N is number of
writes inside of the fence, and M is number of active observers on affected collections.
Every catch up issues yet another query to find the latest oplog entry.

It was extremely inefficient, in terms of both CPU usage and added latency.
After executing write-heavy methods, application process was occupied for many seconds
doing the same thing over and over again.

This change provides a performance improvement for all kinds of workloads.

2015-07-09 09:25:56 -07:00

..

.npm/package

ddp-server does not use faye-websocket directly

2015-04-14 21:34:46 -07:00

crossbar_tests.js

Resolves: ddp package should be split in two

2015-04-14 21:34:46 -07:00

crossbar.js

Extract MongoId into a separate package to reduce the dependencies on minimongo

2015-06-12 11:07:20 -07:00

livedata_server_tests.js

Resolves: ddp package should be split in two

2015-04-14 21:34:46 -07:00

livedata_server.js

Halve heartbeat interval.

2015-06-15 14:12:34 -07:00

package.js

Extract MongoId into a separate package to reduce the dependencies on minimongo

2015-06-12 11:07:20 -07:00

server_convenience.js

webapp and routepolicy need no longer be weak deps

2015-04-14 21:34:46 -07:00

session_view_tests.js

Resolves: ddp package should be split in two

2015-04-14 21:34:46 -07:00

stream_server.js

webapp and routepolicy need no longer be weak deps

2015-04-14 21:34:46 -07:00

writefence.js

Catch up to oplog at most once per write fence

2015-07-09 09:25:56 -07:00