[BUG] VectorCode process killed due to timeout

[edmondop]

"VectorCode process killed due to timeout." appears to me when running :lua require("vectorcode").query("mysql") or similar commands. I am running chromadb 0.6.3 in docker-compose mode using 1 core.

vectorcode query mysql -n 3  36.64s user 4.87s system 137% cpu 30.214 total

 vectorcode ls
Project Root      Collection Size    Number of Files  Embedding Function
--------------  -----------------  -----------------  ------------------------------------
~/code/my_proj                176                 88  SentenceTransformerEmbeddingFunction

sounds like a really long time, how can I troubleshoot it?

[Davidyz]

Hi, if you've got spare cpu cores it might help to allocate more cpu cores to the chromadb process because the query is compute-intensive.

Alternatively, you can also try a different embedding model that produces lower embedding dimensions (the default all-MiniLM-L6-v2 model produces 384-dimension vectors, which is already on the lower end of the spectrum). Some models that produce high-dimensional embeddings claims to perform well even if you truncate the embeddings (that is, getting rid of some dimensions so that they become low-dimensional). snowflake-arctic-embed-m-v2.0 mentioned this on their huggingface page. To use this model with truncation, you can use the following config:

{
  "embedding_params": {
    "model_name": "Snowflake/snowflake-arctic-embed-m-v2.0",
    "truncate_dim": 256,  // this truncate the embeddings to 256 dimensions
  }
}

[Davidyz]

Moving this to discussion for now. We can open a new issue if we find a specific thing (eg. a poorly written piece of code) that is slowing things down.