`SetPayloadOperation` is slower than upserting the entire point
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 304
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 37
Description
Hello!
I am currently utilizing the SetPayloadOperation method to update specific parts of the payload for existing points. Each SetPayloadOperation will have a single point ID. Even when using custom sharding and multiple workers, the performance of this operation is not as good as the upsert method. Theoretically, upsert should be slower since it requires pushing the full payload and vector. However, in practice, upsert is at least 5 times faster than SetPayloadOperation. I am wondering if this behavior is normal. Thank you!
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 reproducing the reported comparison between SetPayloadOperation and upsert, using the single-point updates, custom sharding, and multiple workers described in the issue. Review the client entry points for both operations and measure their relative performance; done means explaining whether the slower behavior is expected or identifying a reproducible performance problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100