concurrent test and calculation of RT and QPS
:purpose: `partition_key: scalar enable partition_key(num_partitions=128)`
verify concurrent DML scenario which
scalar `id`(pk) & `int64_1` created INVERTED index and enable partition_key on `int64_1` field
:test steps:
1. create collection with fields:
'float_vector': 128dim,
'int64_1': is_partition_key
2. build indexes:
IVF_FLAT: 'float_vector'
INVERTED: 'id', 'int64_1'
3. insert 5 million data
4. flush collection
5. build indexes again using the same params
6. load collection
7. concurrent request:
- insert
- delete
- flush
- release
Is there an existing issue for this?
Environment
Current Behavior
argo task: inverted-corn-1719849600 test case name: test_inverted_locust_partition_key_dml_standalone
server:
client pod name: inverted-corn-1719849600-788157396 client error time: 2024-07-01 17:19:07,081 ~ 2024-07-01 19:28:11,949
Expected Behavior
No response
Steps To Reproduce
Milvus Log
No response
Anything else?
test result: