Caching ops
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.5k
- Forks
- 456
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 5
Description
Hello,
I have a collection "people" with ~4000 documents. Sometimes I had to update many of these (~200) at the same time.
I'm calling submitOp() for every single doc to update, this results in the problem, that a connected Browser (which has subscribed the collection) gets 200 single update messages. Because of this, hangs up and doesn't react for ~15 seconds.
Is there a possibility, that this update messages where cached and sent as one single message? Or any other solution that this update-process doesn't affect the browser so much?
About tips I would be glad.
thank you
dsjiern
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing submitOp() through the collection subscription and update-message dispatch paths; the issue names no files or tests. Determine whether batching is supported and define done as preventing a bulk update of roughly 200 documents from overwhelming subscribed browsers, with behavior covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100