You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Resolved conflict in run.py by combining examples from both branches
- Kept mixed workload functionality (insert_fraction, mixed_workload_seed)
- Added new functionality from update.redisearch (engines-file, describe options)
The JSON file should contain an array of engine configuration objects. Each configuration must have a `name` field and follow the same structure as configurations in `experiments/configurations/`:
269
+
270
+
```json
271
+
[
272
+
{
273
+
"name": "my-custom-redis-config",
274
+
"engine": "redis",
275
+
"connection_params": {},
276
+
"collection_params": {
277
+
"algorithm": "hnsw",
278
+
"data_type": "FLOAT32",
279
+
"hnsw_config": {
280
+
"M": 16,
281
+
"DISTANCE_METRIC": "L2",
282
+
"EF_CONSTRUCTION": 200
283
+
}
284
+
},
285
+
"search_params": [
286
+
{
287
+
"parallel": 1,
288
+
"top": 10,
289
+
"search_params": {
290
+
"ef": 100,
291
+
"data_type": "FLOAT32"
292
+
}
293
+
}
294
+
],
295
+
"upload_params": {
296
+
"parallel": 16,
297
+
"data_type": "FLOAT32"
298
+
}
299
+
}
300
+
]
301
+
```
302
+
303
+
**Note:** You cannot use both `--engines` and `--engines-file` at the same time.
304
+
240
305
## How to update benchmark parameters?
241
306
242
307
Each engine has a configuration file, which is used to define the parameters for the benchmark.
0 commit comments