Update of several items kills my app

[darkship]

And if you run these same operations on mongo shell itself, it does not produce such load?

For 1 update, it goes to 4%. That is acceptable.

With and without meteor running ?

Yes

---

I lightened the load through this :
I removed all fields from groupObject that weren’t related to a “member_ids” field using SimpleSchema and Collection2. It dropped the load from 30-40 to 4-8%.

However this is not satisfying.

I wasn’t sure that it’s related to other posts. Now I know that it’s related to live query but I can’t use “Processing High-Velocity Time-Series Data” nor a case where I can use joins or reactive joins .

Performance impact of updates on hidden fields

Hello, For the last few weeks I’ve read quite a lot about meteor. Now, I know fully how to use it, and more or less what it does in the backend. However, I still do not know the internals of meteor very well and that makes me uncertain about a couple of things, like this: Let’s say I have some kind of ‘chatroom’ concept, described by documents like: { id: 1234, name: “Room 1”, participants: [user_id1,user_id2,…] } Now I do not want to send the list of participants over the wire, this is …

Oplog tailing too far behind not helping

Out of curiosity, do those batch processed data updates and inserts need to update the database through the oplog? What happens if this bulk data processing is done during maintenance period where the system is cut off from other client access? Just wondering