If you have questions about how to get the most for your 💲 with Pinecone, let us know. Our team, including Head of Field Engineering Perry Krug, will let you know how to get the best cost-performance for for your workloads in the industry! Here's the DRN announcement Perry references 👇 https://lnkd.in/gJHHPwh3
Had a customer recently migrate from our pod-based indexes to our serverless architecture and went from paying a flat $286/day regardless of their traffic to ~$32/day on weekends and ~$200/day during the week, on track to save them over $1k/month even after doubling their traffic month over month A few points I called out: - They are now paying MUCH less for their non-production workloads rather than having them sit in pod indexes that were mostly idle. For instance, all of their dev indexes combined cost them less than $1 last week on serverless whereas each one alone on pods would have been at least $4 for the week. - Another important consideration here is the alignment of "unit economics" between their users and their cost on Pinecone: their larger and more active users will cost them more, but their smaller ones will cost them less. For example, they have around 145 namespaces on Pinecone. The top one has around 19M records in it and costs them 124 RUs ($0.003) per query, and received around 430k queries in the past month (about $1200). At the other end, one of their smallest namespaces only has 331 records in it which costs them .26 RUs ($0.000006) per query and only received 5 queries in the past month. They have many more of the small ones than the large ones. In a pod-based index, or many other technologies, not only would they be paying to have that data sitting idle but they would also have to deal with the operational overhead of sizing and re-sizing your namespaces (i.e. their customers/tenants) as they grow and change. That doesn't exist with Pinecone's serverless offering. - To some degree, this is the nature of a usage-based system vs an hourly one...on pods they were spending money by the hour regardless of whether they were using the system or not. With serverless, the expectation should be that although they may pay more for a given day of high usage, that will be offset by the times they're paying less or nothing at all. And that the cost grows in line with the success of their business. - For cases where it *DOES* still make sense to pay by the hour and amortise the cost of each read, Pinecone's Dedicated Read Nodes are a perfect fit. The more queries you do, the less each costs and you can scale the infrastructure up and down as needed.