4 ms·

Blog post author here. Let me know if you have any questions!

Lichtso 3y ago
I assume by "http" you mean http1.1 and http2, not http3? Would be nice to differentiate these in the testing as well. WebSockets still seem to be stuck with TCP as rfc9220 [0] is not implemented I think. [0]: https://datatracker.ietf.org/doc/rfc9220/ https://datatracker.ietf.org/doc/rfc9220/
- raoufchebri 3y ago
  Yeah! these are just normal websockets. We're definitely interested in supporting and testing more protocols and ways of accessing postgres and neon as we can. We're also super excited to see the development and adoption of new protocols!
lfmunoz4 3y ago
[dead]
com2kid 3y ago
The axis on all your graphs are unlabeled and have the same scale in both the X and the Y, accordingly I am not sure exactly what is being shown on the graph.
- gmac 3y ago
  Fair point! We'll fix this. In the meantime, the graphs show latency distributions, so the X axis is time (in milliseconds) and the Y axis is a simple count.
- raoufchebri 3y ago
  Thank you. We fixed it now.
FlyingSnake 3y ago
Pardon my ignorance as I'm not aware of these recent developments, but what is a valid use case for this? Why would I put my database into an ephemeral serverless DB[1]? 1: https://news.ycombinator.com/item?id=36684121 https://news.ycombinator.com/item?id=36684121
- gmac 3y ago
  Well, the data is absolutely not ephemeral: it's safely tucked away in S3. But to crib from https://neon.tech https://neon.tech, you might choose Neon because it's scalable, cost-effective, and easy to deploy and manage. Or you might choose it for its copy-on-write branching and point-in-time recovery, all open-source, and all on top of the solid, performant, feature-rich foundation that is Postgres. :)
- raoufchebri 3y ago
  Neon separates storage and compute. The compute part is serverless and can scale up and down on demand. The storage has multiple layers: Safekeepers for durability and Pageservers to reconstruct pages from WAL. The data is also offloaded to S3. Here is a diagram that describes the architecture: https://neon.tech/_next/image?url=https%3A%2F%2Fneon-hwp.dreamhosters.com%2Fwp-content%2Fuploads%2F2023%2F07%2Fimage-8.png&w=3840&q=85 https://neon.tech/_next/image?url=https%3A%2F%2Fneon-hwp.dre...
- tristan957 3y ago
  To follow up on Raouf's comment, here is a blog post[0] that describes Neon's architecture in more detail. [0]: https://neon.tech/blog/architecture-decisions-in-neon https://neon.tech/blog/architecture-decisions-in-neon

I assume by "http" you mean http1.1 and http2, not http3? Would be nice to differentiate these in the testing as well. WebSockets still seem to be stuck with TCP as rfc9220 [0] is not implemented I think. [0]: https://datatracker.ietf.org/doc/rfc9220/ https://datatracker.ietf.org/doc/rfc9220/

raoufchebri 3y ago
Yeah! these are just normal websockets. We're definitely interested in supporting and testing more protocols and ways of accessing postgres and neon as we can. We're also super excited to see the development and adoption of new protocols!

lfmunoz4 3y ago

[dead]

com2kid 3y ago

The axis on all your graphs are unlabeled and have the same scale in both the X and the Y, accordingly I am not sure exactly what is being shown on the graph.

gmac 3y ago
Fair point! We'll fix this. In the meantime, the graphs show latency distributions, so the X axis is time (in milliseconds) and the Y axis is a simple count.
raoufchebri 3y ago
Thank you. We fixed it now.

FlyingSnake 3y ago

Pardon my ignorance as I'm not aware of these recent developments, but what is a valid use case for this? Why would I put my database into an ephemeral serverless DB[1]? 1: https://news.ycombinator.com/item?id=36684121 https://news.ycombinator.com/item?id=36684121

gmac 3y ago
Well, the data is absolutely not ephemeral: it's safely tucked away in S3. But to crib from https://neon.tech https://neon.tech, you might choose Neon because it's scalable, cost-effective, and easy to deploy and manage. Or you might choose it for its copy-on-write branching and point-in-time recovery, all open-source, and all on top of the solid, performant, feature-rich foundation that is Postgres. :)
raoufchebri 3y ago
Neon separates storage and compute. The compute part is serverless and can scale up and down on demand. The storage has multiple layers: Safekeepers for durability and Pageservers to reconstruct pages from WAL. The data is also offloaded to S3. Here is a diagram that describes the architecture: https://neon.tech/_next/image?url=https%3A%2F%2Fneon-hwp.dreamhosters.com%2Fwp-content%2Fuploads%2F2023%2F07%2Fimage-8.png&w=3840&q=85 https://neon.tech/_next/image?url=https%3A%2F%2Fneon-hwp.dre...
tristan957 3y ago
To follow up on Raouf's comment, here is a blog post[0] that describes Neon's architecture in more detail. [0]: https://neon.tech/blog/architecture-decisions-in-neon https://neon.tech/blog/architecture-decisions-in-neon