uri
CDCloudflare Developers
•Created by uri on 9/29/2024 in #vectorize
I noticed on this page "https://
I need the service to identify various characteristics independently, such as face vectors, license plate vectors (each with different sizes and meanings), and other attributes. Currently, I use separate indexes for each type of attribute, as they vary in vector size and meaning. Additionally, I use a separate namespace for each client. When searching for a similarity vector, I want the query to be limited to vectors within the corresponding client's data.
However, I expect to have more than 1,000 clients in the future(each client has muti vectors), and the number of namespaces may become a limiting factor. Given this, would you recommend a different approach to structuring the data? Should I be concerned about the scalability of namespaces as the number of clients grows?
3 replies