Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
GabeWeiss_
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
1.
▲
by
GabeWeiss_
3y ago
Fair enough, I'm not (obviously) as familiar with the AWS systems and how the price to performance ratio works out for all the products.
2.
▲
by
GabeWeiss_
3y ago
Of course, I was simplifying. It's always more complicated doing a migration. :)
3.
▲
by
GabeWeiss_
3y ago
Yes, but QPS vs. "queries to the API". The difference is the time slice. I should have been more explicit. The key here really is the time function between the numbers. That the AWS blog calls out trillions of API calls isn't
4.
▲
by
GabeWeiss_
3y ago
Parts, yes. In reference to the specifics mentioned in here though, those services run on Infra Spanner, not Cloud Spanner, but they're the same stack. The main reason things like Gmail, Ads, etc haven't swapped into GCP is becaus
5.
▲
by
GabeWeiss_
3y ago
Tell me more (bonus points if you find me on LinkedIn or other social because tracking comment responses on HN is really rough). I'd love feedback you have so I can bring it back to the product team!
6.
▲
by
GabeWeiss_
3y ago
Really glad to hear! Please find me on social media or LinkedIn and let me know how it goes for you using the PG layer. I'd love to hear more feedback.
7.
▲
by
GabeWeiss_
3y ago
You can! Spanner has a free trial: https://cloud.google.com/spanner/docs/free-trial-instance . Keep in mind, that per-request pricing isn't free unless you stay under the free tier. So just take a look at what
8.
▲
by
GabeWeiss_
3y ago
The DeWitt clause is only there to prevent badly written performance data from getting attention it shouldn't. If anyone writes a good benchmark (good process, not good results, necessarily) to bring to us, our product teams absolutely
9.
▲
by
GabeWeiss_
3y ago
More specifically, infra and cloud Spanner are the same stack. So they've progressed together hugely since 2013. :) The real differences between the two are more about the internal tooling we (Google) have around infra that's buil
10.
▲
by
GabeWeiss_
3y ago
But that's kind of a moot point. I mean, if you're even looking at the likes of DynamoDB or Spanner, it's because you need the scale of those engines. PostgreSQL is fantastic, and even working for Google, I 100% agree with yo
11.
▲
by
GabeWeiss_
3y ago
100% this, and even though I work for Google I absolutely agree. BUT, for the folks that need it, PostgreSQL just DOESN'T cut it, so it's why we have databases like DynamoDB, Spanner, etc. Arguing that we should "Just use PG&
12.
▲
by
GabeWeiss_
3y ago
True, but one would hope that both sides in this case would be putting their best foot forward. Getting peak performance out of right sizing your DB is part of that discussion. I can't imagine AWS would put down "126 million QPS&q
13.
▲
by
GabeWeiss_
3y ago
Infra and Cloud Spanner are the same stack. Having those services run on infra is more about the legacy of tooling to shift it rather than anything around performance or ability to handle it
14.
▲
by
GabeWeiss_
3y ago
Infra and Cloud Spanner are the same stack. Having those services run on infra is more about the legacy of tooling to shift it rather than anything around performance or ability to handle it.
15.
▲
by
GabeWeiss_
3y ago
Just as a hand in the air...Be careful about what you're comparing here. # of API calls over a period of time is...largely irrelevant in the face of QPS. I can happily write a DDOS script that massively bombards a service, but if that
16.
▲
by
GabeWeiss_
3y ago
My PM also reminded me, depending on the data set size too, if it's bigger than the buffer cache, we might see some improvements over PG as well from that (we've made memory improvements around that which might help potentially).
17.
▲
by
GabeWeiss_
3y ago
I'm assuming you mean "I start using this under a free dev license, and want to shift up to the paid production version"? And what that looks like? If that's the case, I don't know yet. That's literally being d
18.
▲
by
GabeWeiss_
3y ago
The improvements we've made on the read side of things likely won't affect the geo data directly, BUT, depending on what other aggregate data you're combining with the geo data you might see some improvement from the columnar
19.
▲
by
GabeWeiss_
3y ago
It really is, yes. I can't go into a lot of detail on the "why" because it's not open source and the product team would murder me...but I highly encourage folks to try it for themselves. Nothing else convinced me until I
20.
▲
by
GabeWeiss_
3y ago
As a heads up, we're unlikely to make the codebase for it open. I might be able to convince the product team to open source some components of it (our GM has talked about this before in a couple articles), the whole thing won't be
21.
▲
by
GabeWeiss_
3y ago
No worries on the negativity! I totally understand. No one likes to have time wasted. :( I'm getting the more detailed info on the cache use-case to the eng team just so they're aware. Also, the can't disable it...so funny st
22.
▲
by
GabeWeiss_
3y ago
We don't have specific details yet about licensing or pricing. Stay tuned as we get closer to GA. Having said that, we're pushing hard for a free usage tier and the product team isn't pushing back. :)
23.
▲
by
GabeWeiss_
3y ago
We encourage folks to draw their own conclusions, but we have done comparisons and ours is more efficient and produces faster results. I only say test yourself because I can't give specific details of how/why, so don't take m
24.
▲
by
GabeWeiss_
3y ago
Not for Omni no. End-users are responsible for any HA/DR/Replication needs. Cloud AlloyDB has all of it built in, but since it was so tightly tied to the Cloud infrastructure it was simplified for Omni.
25.
▲
by
GabeWeiss_
3y ago
100% I'm a huge PG fan as well. This should absolutely be "PG + performance and QoL improvements". Where it's not, we want to hear about it.
26.
▲
by
GabeWeiss_
3y ago
Code improvements. Indices aren't taken into account at all since that's so workload dependent. Having said that, the index advisor can make finding the right indices to improve performance there more easily as well. Vacuum manage
27.
▲
by
GabeWeiss_
3y ago
Okay, I can't speak for ALL engineering teams, but at the very least I know THIS engineering team absolutely does.
28.
▲
by
GabeWeiss_
3y ago
Yeah, I know. Apologies. Stay tuned though! For the tech preview launch we really focused on a golden path (narrow). We'll be expanding compatibility as we march towards GA.
29.
▲
by
GabeWeiss_
3y ago
It's twice as fast as out of the box PG for most things, and up to 100x faster for reads, depending on what you're doing. So there's that. Also, from a manageability, on top of the index advisor, there's also vacuum mana
30.
▲
by
GabeWeiss_
3y ago
WHAT DO YOU MEAN?! RAAAAAGE!! ;) I mean, if someone legitimately finds workloads that aren't performing well, our engineering team SHOULD want to know about it, right?
More ›