-
Type: Bug
-
Resolution: Duplicate
-
Priority: Minor - P4
-
None
-
Affects Version/s: 2.5.0
-
Component/s: Internal Code
-
None
-
ALL
Tailing a capped collection with await_data is sometimes recommended as a simple pub / sub system. But if no documents are being inserted into the collection, each tailable cursor checks for new documents every 2ms. In my system, this means that 10 subscribers spin the CPU at 36%.
A better solution would be a condition variable per collection that is notified when documents are inserted.
- duplicates
-
SERVER-9580 Multiple tailable cursors against the same collection shows high cpu usage on server
- Closed
- is related to
-
SERVER-18184 Add awaitData support to getMore command
- Closed