Cloudflare Developers•2mo ago

I noticed on this page "https://developers.cloudflare.com/vectorize/platform/limits/" that the curre

I noticed on this page "https://developers.cloudflare.com/vectorize/platform/limits/" that the current limits are 100 indexes and 1,000 namespaces. While this might be sufficient for testing, it's far from enough for production use. Are there any plans to scale these limits—at least by a couple of orders of magnitude? Something closer to 1,000,000 or more would be ideal.

18 Replies

uriOP•2mo ago

I want to building my SaaS around 'Vectorize' as I really like the platform. However, with the current limitations in place, if these are expected to remain for the foreseeable future, I won't be able to use it for my needs. Additionally, dedicated functions or tools for backup and restore are essential for anyone looking to use this platform in production environments. Could someone provide insight into the current roadmap for 'Vectorize' in terms of limitations and development? What can we expect in the near future?

Rihan•2mo ago

With terminology, are Vectorize indexes and databases exchangeable terms, or are indexes the preferred way to refer to them?

Rihan•2mo ago

This is on Pages -> Settings -> Bindings -> Add -> Vectorize database

Ashley•2mo ago

Is the billing page broken? I clicked view next to monthly usage on the Vectorize dashboard and I get an oops page 😅

echoes221•2mo ago

Remix + Cloudflare - running wrangler types generates the correct vectorize types, however the proxy stub doesn't exist in the loader (cloudflareDevProxyVitePlugin). Is this due to beta?

  const {
    params,
    context: { cloudflare },
  } = args;
 
  if (!cloudflare.env.VECTORIZE) { // <-- doesn't exist
    console.log("no key"); 
    return;
  }

  const {
    params,
    context: { cloudflare },
  } = args;
 
  if (!cloudflare.env.VECTORIZE) { // <-- doesn't exist
    console.log("no key"); 
    return;
  }

sathoro•2mo ago

can the 1,000 namespaces per index limit be easily increased? we use Pinecone but was looking at using Vectorize for a new feature and this limit is really putting us off

Rubi•2mo ago

yes, vectorize is currently not available on local

echoes221•2mo ago

Thanks for the update!

Jerome•2mo ago

We're currently working on supporting local binding for vectorize, hopefully completed this month :soontm:

echoes221•2mo ago

That would be great, thank you. In the meantime I’m generating embeddings using workers ai, then storing them in pg vector / querying in Postgres, seems to work well enough!

uriOP•2mo ago

what is "local binding for vectorize" mean?

Ashley•2mo ago

For a lot of Cloudflare products, you can use a similar version of the product locally. So when you run “wrangler dev”, the binding still works, so you can run/test locally - for Vectorize, that isn’t available yet, so you have to run it remote to test it (either deploy, or wrangler dev remote)

crunchy•2mo ago

Hi is there an additional information on the eventual consistency behaviour, can I assume the vectors are available for search in order? does the mutation identifier have an meaning? can it be used as a high water mark? I have a use case were a want to group vectors, it's tricky to do without knowing when vectors will be availible? presumable without a hwm I'd have to use a queue with some kind of back off but that won't help if the vectors are not indexed in order. presumble then the only solution would be repair on each read but i'm capped to 100 nearest neighbours.

Jerome•2mo ago

Hi! The DB state is eventually consistent, and all mutations (upsert, insert, delete, create metadata index, ...) are processed in the strict order they were given to the API. This means the index state is always reflecting all the mutations that were given to the API up to the last applied mutation, processed in order. The mutationId acts as a high watermark indeed, you can compare the mutationId returned by any mutation operation and the one you get by calling https://developers.cloudflare.com/vectorize/reference/client-api/#get-index-info ; this will return the vector count, the last applied mutationId (again, in the sequence ordered as provided to the API) and the last UTC datetime this mutation corresponds to (useful if you don't keep track of the mutationIds)

Unknown User•2mo ago

Message Not Public

vvotekeb•2mo ago

Does anyone know of any methods to create a backup for an index? I'm looking for a script/code that can pull all the data from one index and insert it to another.

kingmesal•2mo ago

I'm very eager to move off of pinecone, purely from a simplicity perspective. I can work around some limitations, however there are a couple big blockers. 1. Metadata filtering has to support more than =, !=... E.g. <, <=, >=, > ... Even a filter for in list or not in list. 2. Not a blocker, but having an actual view in the dashboard would be a big help 3. The comment I saw above about local Wrangler support removes the other blocker

Bryan•2mo ago

I can't understand why vectorize has so many limits. I don't think I can develop a production-level project under current limits. Compared to Pinecone, which has ZERO limits as long as I pay for what I need. Really hope one day all limits go away.

Gaming

Programming

I noticed on this page "https://developers.cloudflare.com/vectorize/platform/limits/" that the curre