Hi , Please help in acheiving my AIM, as explained below with reason. AIM : want to have 1 Vector D
Hi , Please help in acheiving my AIM, as explained below with reason.
AIM : want to have 1 Vector DB per User .. for this design, plan to have created 50000 Vectorize Bindings (Upper Limit by CF) to the Worker (in first deployment) .. then, as new user signs-up pick a deterministic allocation of 1 Binding from "available pool of bindings" ..
What after 50000 users signed up ? .. create a new CF account and somehow find a way to direct the traffic based on a KV Map which keeps track for Worker Account and Binding ID with-in that worker, allocated for the user.
Question : is there a smarter way to acheive the AIM ?
Reason for My Ugly Design : Upfront Heavy Cost Incurred, for "just ONE" query done .. AFTER "FIRST" query, the incremental costs for query are very minimal .. so, if there are many NAMESPACE seperated users in ONE Vectorise Index .. Just ONE Active user will baloon-up the bill for rest dormant users (who never queries DB in that month)
This will result in ONLY ONE PAID User, while Vectorize will costing me for ALL Users in that Index.
Example :
CF Pricing : ((queried vectors + stored vectors) * dimensions * ($0.01 / 1,000,000)) + (stored vectors * dimensions * ($0.05 / 100,000,000))
Assume : stored vectors = 4200000, dimension = 1024, duration = 1 month
Case-1 : ZERO QUERIES , Total Cost = $2.1504
Case-2 : THREE QUERIES, Total Cost = $45.15

AIM : want to have 1 Vector DB per User .. for this design, plan to have created 50000 Vectorize Bindings (Upper Limit by CF) to the Worker (in first deployment) .. then, as new user signs-up pick a deterministic allocation of 1 Binding from "available pool of bindings" ..
What after 50000 users signed up ? .. create a new CF account and somehow find a way to direct the traffic based on a KV Map which keeps track for Worker Account and Binding ID with-in that worker, allocated for the user.
Question : is there a smarter way to acheive the AIM ?
Reason for My Ugly Design : Upfront Heavy Cost Incurred, for "just ONE" query done .. AFTER "FIRST" query, the incremental costs for query are very minimal .. so, if there are many NAMESPACE seperated users in ONE Vectorise Index .. Just ONE Active user will baloon-up the bill for rest dormant users (who never queries DB in that month)
This will result in ONLY ONE PAID User, while Vectorize will costing me for ALL Users in that Index.
Example :
CF Pricing : ((queried vectors + stored vectors) * dimensions * ($0.01 / 1,000,000)) + (stored vectors * dimensions * ($0.05 / 100,000,000))
Assume : stored vectors = 4200000, dimension = 1024, duration = 1 month
Case-1 : ZERO QUERIES , Total Cost = $2.1504
Case-2 : THREE QUERIES, Total Cost = $45.15





