6 ms·

While in EA (early access), there's no additional cost of Prisma Postgres, you're effectively getting a free Postgres db. The pricing you are citing is for Acc

While in EA (early access), there's no additional cost of Prisma Postgres, you're effectively getting a free Postgres db. The pricing you are citing is for Accelerate, which does advanced connection pooling and query caching across 300 POPs globally. All that being said, we'll def address the "can you pls make Prisma Postgres pricing simpler to grok?" question before we GA this thing. Thanks for the feedback!

aurareturn 2y ago
Does a simple selection query count the same as a 50 line query joining many tables and doing aggregates?
- gniting 2y ago
  Yes
endorphine 2y ago
What makes its connection pool "advanced"?
- gniting 2y ago
  - autoscaling - connection pool size limits - query limits - multi-region support out of the box more here: https://www.prisma.io/docs/accelerate/connection-pooling https://www.prisma.io/docs/accelerate/connection-pooling also recommend trying out the Accelerate speed test to get a "feel for it": https://accelerate-speed-test.prisma.io/ https://accelerate-speed-test.prisma.io/
  - IceDane 2y ago
    I'm wondering big the prisma overhead is here. I know that historically, prisma has been very slow - the sidecar process and the generic protocol and database agnosticism come with a steep cost, and the numbers shown in the benchmark both seem rather low to me. 4x the performance of "very slow" isn't super impressive.. but of course, I can't verify this right now since I don't have access to machine where I can duplicate this and run some raw postgres queries to compare.
    - eampiart 2y ago
      The global caching gets even more interesting and beneficial when the end users are all over the globe, and you're caching queries that simply take longer to execute on the db. You'll save time both on latency and compute that way. For example, everything running on the speedtest is through a single internal Accelerate project so we have some data: the overall average is 58x faster, with 779.53 ms served from origin and 13.28 ms served from cache. Nonetheless, we absolutely have room for improvement on the ORM in terms of performance, and are working on those as well!
Aeolun 2y ago
I think from my perspective there’s some cognitive dissonance when I imagine myself getting the free plan with a cool 60k queries included, and then switching to the paid plan, and finding that that I still have a cool 60k queries included. Wat? I rationally realize there is a price/usage point where this makes sense, but emotionally it doesn’t feel good. Start the plan at $59 and include 2M queries.
- gniting 2y ago
  Thanks for the feedback!
avinassh 2y ago
is there any page which explains how does Accelerate works? I am interested knowing the internal technical details
- gniting 2y ago
  If you mean beyond the product page and our docs, then no. Accelerate is not an OSS product from Prisma. All that being said, if there are specific questions that you have which relate to a use case, ask away!
- ComputerGuru 2y ago
  It sounds like a clone of Cloudflare hyperdrive and others: https://developers.cloudflare.com/hyperdrive/get-started/ https://developers.cloudflare.com/hyperdrive/get-started/
  - gniting 2y ago
    Cloudflare announced Hyperdrive on September 28, 2023 Prisma announced Accelerate on January 16, 2023 But you are right, they are close in functionality though Hyperdrive requires a CF Worker to operate.
martin82 2y ago
When I looked at your pricing, this were my thoughts: 1) 60k queries? I burn through that in an hour. All it takes is the Google bot and some shitty AI scraper to come along and crawl our site - which happens every single day. 2) $18 per million? I don't know how many queries I need per day, at the moment, but give 1), I will surely burn through a million dozens of times oer months... ...at which point this thing will be just as expensive as an RDS instance on AWS, potentially even more so if we hit traffic peaks (every single user causes hundreds of queries, if not thousands). 3) I don't even understand who to interpret the egress cost. No idea how to predict what the pricing will be. Maybe some calculator where we can slot in the relevant estimated values would be nice?
- eampiart 2y ago
  Thanks for walking through your thinking, feedback taken! What's your take on the pricing calculator? We've been working on an improved version, and would love to hear your thoughts on this. In your case, what inputs would you find helpful to put in to arrive at a calculation, considering that you're unsure about projecting both queries and egress? How would you go about putting in estimated values for those?

aurareturn 2y ago

Does a simple selection query count the same as a 50 line query joining many tables and doing aggregates?

gniting 2y ago
Yes

endorphine 2y ago

What makes its connection pool "advanced"?

gniting 2y ago
- autoscaling - connection pool size limits - query limits - multi-region support out of the box more here: https://www.prisma.io/docs/accelerate/connection-pooling https://www.prisma.io/docs/accelerate/connection-pooling also recommend trying out the Accelerate speed test to get a "feel for it": https://accelerate-speed-test.prisma.io/ https://accelerate-speed-test.prisma.io/
- IceDane 2y ago
  I'm wondering big the prisma overhead is here. I know that historically, prisma has been very slow - the sidecar process and the generic protocol and database agnosticism come with a steep cost, and the numbers shown in the benchmark both seem rather low to me. 4x the performance of "very slow" isn't super impressive.. but of course, I can't verify this right now since I don't have access to machine where I can duplicate this and run some raw postgres queries to compare.
  - eampiart 2y ago
    The global caching gets even more interesting and beneficial when the end users are all over the globe, and you're caching queries that simply take longer to execute on the db. You'll save time both on latency and compute that way. For example, everything running on the speedtest is through a single internal Accelerate project so we have some data: the overall average is 58x faster, with 779.53 ms served from origin and 13.28 ms served from cache. Nonetheless, we absolutely have room for improvement on the ORM in terms of performance, and are working on those as well!

Aeolun 2y ago

I think from my perspective there’s some cognitive dissonance when I imagine myself getting the free plan with a cool 60k queries included, and then switching to the paid plan, and finding that that I still have a cool 60k queries included. Wat? I rationally realize there is a price/usage point where this makes sense, but emotionally it doesn’t feel good. Start the plan at $59 and include 2M queries.

gniting 2y ago
Thanks for the feedback!

avinassh 2y ago

is there any page which explains how does Accelerate works? I am interested knowing the internal technical details

gniting 2y ago
If you mean beyond the product page and our docs, then no. Accelerate is not an OSS product from Prisma. All that being said, if there are specific questions that you have which relate to a use case, ask away!
ComputerGuru 2y ago
It sounds like a clone of Cloudflare hyperdrive and others: https://developers.cloudflare.com/hyperdrive/get-started/ https://developers.cloudflare.com/hyperdrive/get-started/
- gniting 2y ago
  Cloudflare announced Hyperdrive on September 28, 2023 Prisma announced Accelerate on January 16, 2023 But you are right, they are close in functionality though Hyperdrive requires a CF Worker to operate.

martin82 2y ago

When I looked at your pricing, this were my thoughts: 1) 60k queries? I burn through that in an hour. All it takes is the Google bot and some shitty AI scraper to come along and crawl our site - which happens every single day. 2) $18 per million? I don't know how many queries I need per day, at the moment, but give 1), I will surely burn through a million dozens of times oer months... ...at which point this thing will be just as expensive as an RDS instance on AWS, potentially even more so if we hit traffic peaks (every single user causes hundreds of queries, if not thousands). 3) I don't even understand who to interpret the egress cost. No idea how to predict what the pricing will be. Maybe some calculator where we can slot in the relevant estimated values would be nice?

eampiart 2y ago
Thanks for walking through your thinking, feedback taken! What's your take on the pricing calculator? We've been working on an improved version, and would love to hear your thoughts on this. In your case, what inputs would you find helpful to put in to arrive at a calculation, considering that you're unsure about projecting both queries and egress? How would you go about putting in estimated values for those?