microsoft / microsoft/SPTAG

KMeans clustering

Open
#403 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
5k
Forks
622
Avg merge
8h 37m
Merged PRs (30d)
5

Description

Regarding spann, I would like to ask a few questions, as follows:

  1. Regarding KMeans clustering, what is the limit for each cluster center? If it exceeds this limit, will it be re divided into one or multiple layers?
  2. When does the centroid in memory need to be updated after clustering is completed?
  3. After completing clustering, should the new vector data be written directly into posting list in the disk or stored as centroids in memory?
  4. When will KMeans clustering be done again?
  5. There are too many clusters, will they be clustered with KMeans clustering algorithms again?
  6. What is the difference between sptag and sptag++ ?
  7. One question about Hierarchical data partition and partial search, as follows:
    Does each query require two steps: 1) Distributed dispatch and 2) Local Search?
    What are the transactions for these two steps?
    image

Looking forward to your reply.
Thanks very much.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by reviewing the SPTAG documentation and architecture material for KMeans, hierarchical partitioning, partial search, and the distinction between SPTAG and SPTAG++; done would require maintainer-confirmed answers or linked documentation.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend, distributed-systems
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.