alibaba / alibaba/zvec

[Feature]: Turbo Integration

Open
#323 0 comments 0 reactions 1 assignee Claimed by @richyreachy View on GitHub
feature
Dominant language
C++
Stars
15.9k
Forks
998
Avg merge
4d 7h
Merged PRs (30d)
34

Description

### Problem / Motivation

Currently, the internal implementation of metric distances is scattered across multiple files, which causes confusion to spot and fix problem during runtime. Moreover, it's quite difficult to tell which distance function is actually being invoked.

In addition, some quantization metas are concatenated after vector data, increasing the dimensionality and making the resulting dimensions inconsistent with those of the original input.

### Proposed Solution

```python
1. Use a unified interface to select the best optimized distance function as per runtime march
2. Every metric distance function is coherently implemented in a single unified function
3. Versions of distance functions, including single and batch, are organized into separate folders respectively,
4. Extra meta is specified explicitly, rather than being mixed with vector dimensions
```

### Alternatives Considered

_No response_

### Affected Area

{"label" => "C++ Core (storage, indexing)"}

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.