Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
phamilton
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
91.
▲
by
phamilton
3y ago
I really like the idea of canonical maps/morphisms. The idea is that there exists one and only one possible implementation of a given type transformation. For code constructed of canonical morphisms, the compiler can prove correctness.
92.
▲
by
phamilton
3y ago
There's also a difference between reading K&R and being comfortable with conventional C. Reading through source code from a mature project like PostgreSQL or the Linux kernel is very different from just knowing how malloc and free
93.
▲
by
phamilton
3y ago
It never recovered from the loss of gentoo-wiki
94.
▲
by
phamilton
3y ago
I sent an email and it was blocked: "Recipient address rejected: Access denied."
95.
▲
by
phamilton
3y ago
Digging a bit, it seems the wait-list really started to be a thing in 2019. > It takes a ton of investment. I'm not an expert, but for an "assembled by hand" luxury product it seems like incremental capacity is much lower
96.
▲
by
phamilton
3y ago
> max capacity As determined by what? Probably the current manufacturing facilities that they have strategically chosen not to expand.
97.
▲
by
phamilton
3y ago
Did he have some way to keep them straight? Seems like a recipe for forgetting which one is real and which one is fake.
98.
▲
by
phamilton
3y ago
We have this with APM monitoring, where every SQL query in the application becomes a span in a trace. It is very useful. We can quickly see the specific parameters that make an otherwise fast query slow.
99.
▲
by
phamilton
3y ago
> I would strongly doubt that count( ) without a where clause isn’t already highly optimized It's actually not well optimized in PostgreSQL because of MVCC. See https://wiki.postgresql.org/wiki/Slow_Counting TL
100.
▲
by
phamilton
3y ago
> I'm guessing this won't be a major problem. I don't know any proficient Rust or C++ developers that are not also proficient C developers. There's a growing trend in high level languages like Ruby/Elixir/no
101.
▲
by
phamilton
3y ago
With an AGPL license, does that make it unlikely to be included in hosted environments like RDS? My understanding of the spirit of the license is that it should be fine as long as modifications are made available. Anyone know of any existin
102.
▲
by
phamilton
3y ago
A proprietary product, but AWS Aurora Clones are CoW.
103.
▲
by
phamilton
3y ago
A reason I would still bias towards postgres is the maturity of managed solutions (including decoupled compute/storage solutions like Aurora and AlloyDB). Are managed "proper OLAP DB" solutions competitive with managed RDBMS
104.
▲
by
phamilton
3y ago
That's true, however a lot of spot usage ends up being heavily diversified across instance types in order to avoid momentary supply issues and optimize cost. Across different families, CPU performance can vary by a decent amount.
105.
▲
by
phamilton
3y ago
My hope is that managed data layers become more available and the problem space of "custom data structures and indexes" can be decoupled from the even harder parts of writing a database. Projects like pgrx (postgres extensions in
106.
▲
by
phamilton
3y ago
> The authors claim it guarantees exactly-once delivery I find this definition has morphed from one meaningful to developers into one queue implementations like to claim. I've learned this generally means "multiple inserts will
107.
▲
by
phamilton
3y ago
I've explored this space pretty thoroughly, including the Dynamo approach you've described. Dynamo does not have a strict guarantee on when items get deleted: TTL typically deletes expired items within a few days. Depending on
108.
▲
by
phamilton
3y ago
Yep. OOMs are the most common cause. It's definitely low frequency. On the order of one in a billion. For some systems that's once a year. For us that's once a week. If that's an important job and it just gets dropped, t
109.
▲
by
phamilton
3y ago
I can share our experience with RabbitMQ/SQS/Sidekiq. Our two major issues have been around the retry mechanism and resource bottlenecks. The key retry problem is "What happens when a worker crashes?". RabbitMQ solves th
110.
▲
by
phamilton
3y ago
I also question the revenue claim. Google has a lot of revenue. Pinterest, Hashicorp, Uber, Twitch, Dropbox, etc. all have a good amount of golang and collectively have a lot of revenue. It might need a few more years to tip the scale, but
111.
▲
by
phamilton
3y ago
> but no more databases Sort of. Twice as many rails hosts means more DB connections which generally means more load/memory on the DB or more load/memory on the external connection pooler. It's only a bit of incremental lo
112.
▲
by
phamilton
3y ago
LocalSet does not require Send. https://docs.rs/tokio/latest/tokio/task/struct.LocalSet.html EDIT: Sorry to join in the multiple responses. Clarity for others: "current_thread" by itself does n
113.
▲
by
phamilton
3y ago
Not quite what you are describing, but sort of in the same space, are SSR heavy frameworks like Next.js. Those solve problems by having the backend do most of the heavy lifting and streaming UI updates to the browser. This makes the browser
114.
▲
by
phamilton
3y ago
The writer also has traffic that can attempt to acquire the locks. Reads and writes (though our highest volume read traffic is reader only). Contention from the standbys do not get communicated to the writer.
115.
▲
by
phamilton
3y ago
We got hit with a good bit of the postgres iceberg this week. VACUUM by default runs with the TRUNCATE option. This will, if possible and valuable, truncate the heap and return those pages to the operating system. This operation takes an Ac
116.
▲
by
phamilton
3y ago
The problem was that it was the same one machine that always had the extra 50% traffic. The eventual fix from Amazon was to randomly select in a tie breaker so that each machine had, on average, 2.1 concurrent requests (assuming 10 machines
117.
▲
by
phamilton
3y ago
We've used both round robin and least outstanding connections in AWS and found many really weird phenomena over the years. In general, LOC is more forgiving for uneven workloads, especially for Ruby services. If a slow request hits, th
118.
▲
by
phamilton
3y ago
> I've been unimpressed with datadog apm, which has no affordable configuration FWIW we sample in datadog APM and it works fine to control costs, I'm not sure what issues you hit.
119.
▲
by
phamilton
3y ago
https://opentelemetry.io/docs/concepts/sampling/ describes it as Head/Tail sampling, but in practice with vendors I see it as Ingestion sampling and Index sampling. We send all our spans to be ingested,
120.
▲
by
phamilton
3y ago
Please share more!
More ›