mirror of
https://github.com/qdrant/landing_page.git
synced 2026-09-28 15:38:33 +02:00
docs: Proofread and updated snippets (#1243)
This commit is contained in:
@@ -13,6 +13,7 @@ Qdrant exposes administration tools which enable to modify at runtime the behavi
|
||||
|
||||
A locking API enables users to restrict the possible operations on a qdrant process.
|
||||
It is important to mention that:
|
||||
|
||||
- The configuration is not persistent therefore it is necessary to lock again following a restart.
|
||||
- Locking applies to a single node only. It is necessary to call lock on all the desired nodes in a distributed deployment setup.
|
||||
|
||||
|
||||
@@ -535,8 +535,7 @@ client.upsert(
|
||||
```
|
||||
|
||||
```typescript
|
||||
|
||||
client.upsertPoints("{collection_name}", {
|
||||
client.upsert("{collection_name}", {
|
||||
points: [
|
||||
{
|
||||
id: 1111,
|
||||
|
||||
@@ -10,6 +10,7 @@ aliases:
|
||||
Different use cases require different balances between memory usage, search speed, and precision. Qdrant is designed to be flexible and customizable so you can tune it to your specific needs.
|
||||
|
||||
This guide will walk you three main optimization strategies:
|
||||
|
||||
- High Speed Search & Low Memory Usage
|
||||
- High Precision & Low Memory Usage
|
||||
- High Precision & High Speed Search
|
||||
|
||||
Reference in New Issue
Block a user