SetPayloadOperation is slower than upserting the entire point

[sebastiancojocariu97]

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!

[joein]

Hi @sebastiancojocariu97 , could you provide an example of your request?
How do you specify points?
What is the wait parameter value?
Do you use grpc or rest?

[sebastiancojocariu97]

Hello!
I am using grpc and I am packaging the requests (which are sent in parallel for each shard_id using multiprocessing) as follows:

update_operations = []
for obj, target_fields in batch:
        update_op = qdrant_models.SetPayloadOperation(
            set_payload=qdrant_models.SetPayload(
                payload=obj.model_dump(by_alias=True, include=target_fields),
                points=[obj.hash],
                shard_key=shard_id,
            )
        )
        update_operations.append(update_op)

await client.batch_update_points(collection_name=collection_name, update_operations=update_operations, wait=False)