Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
arjunnarayan
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
61.
▲
by
arjunnarayan
9y ago
Thank you as well! I will almost certainly reach out to you about this at some point!
62.
▲
by
arjunnarayan
9y ago
If you are using Joins in an OLTP setting, everything should work absolutely as you might expect. "Functional" is our caveat that if you run Joins across your data in an OLAP setting, it will work, but it may not be the most perfo
63.
▲
by
arjunnarayan
9y ago
This is more my personal opinion, and perhaps more revealing my ignorance on the existing equivalent tools in the Rust ecosystem, but here is a list of some of the Go tools we use when developing CockroachDB: 1. gofmt and goimports really h
64.
▲
by
arjunnarayan
9y ago
The latter. NTP only checks and corrects clock offsets every so often. If the "hardware"[1] clock undergoes offset shifts at random times because of VM pauses this won't get fixed immediately until the next NTP sync. This get
65.
▲
by
arjunnarayan
9y ago
We were told that the slides would be uploaded by Applicative (hence we didn't post a copy), but we can't seem to find it on the internet either, so here's a copy from our Google drive: https://drive.google.com
66.
▲
by
arjunnarayan
9y ago
The short story is we do need high capacity network links to function well. By "high capacity" I mean at least double digit megabit links between your datacenters. A query that inherently requires shuffling because the data is geo
67.
▲
by
arjunnarayan
9y ago
Not in a rigorous fashion yet, but we will talk about that soon. I've got a couple other comments on this post talking about performance benchmarking: https://news.ycombinator.com/item?id=14308770 and https:/
68.
▲
by
arjunnarayan
9y ago
We have a post on why we chose Go, from a year and a half ago: https://www.cockroachlabs.com/blog/why-go-was-the-right-choi... More technically, here's a somewhat random set of thoughts on the subject: The Go GC i
69.
▲
by
arjunnarayan
9y ago
This feature is planned, but I cannot give you a concrete timeline. We want to do this right, and we need other parts in place to do this with high performance, in a transactionally consistent fashion, in the face of high contention, and fo
70.
▲
by
arjunnarayan
9y ago
[Cockroach Labs engineer here] For just a couple billion rows and a dozen joins, a single node will suffice (with the caveat that you really want at least 3 nodes because CockroachDB is built for replication and fault-tolerance and you'
71.
▲
by
arjunnarayan
9y ago
No. Once your latency goes beyond single digit seconds, performance will probably collapse. Too many subsystems would time out. in theory it could be made to work (with terrible performance, and extremely long commit-waits due to having to
72.
▲
by
arjunnarayan
9y ago
Not yet, but it's on our roadmap.
73.
▲
by
arjunnarayan
9y ago
[Cockroach Labs engineer here working on performance benchmarking] We have load generators for YCSB (just raw key-value ops in a firehose) and TPC-H (very complicated read-only queries) running right now, and we're about to start runni
74.
▲
by
arjunnarayan
9y ago
So performance is complicated. Right now, we’re performance testing CockroachDB regularly, and everything is out in the open. Everything we do is tracked with a GitHub issue with the “perf:” prefix, if you want to follow along. Here are all
75.
▲
by
arjunnarayan
9y ago
I have ported a MySQL-based ActiveRecord Rails app that was somewhat complicated to Postgres, and then on to CockroachDB. It works pretty well, so I'd give it a go. We're also committed to supporting ActiveRecord via the Postgres
76.
▲
by
arjunnarayan
10y ago
Subscribe to the free once-a-week. If you like it, upgrade to the paid once-a-day.
77.
▲
by
arjunnarayan
10y ago
False. Bezos was EECS at Princeton, and then went to work in finance for ~8 years before starting Amazon.com
78.
▲
Gryadka is not Paxos, so it's probably wrong
(tschottdorf.github.io)
132 points
by
arjunnarayan
10y ago
|
42 comments
79.
▲
by
arjunnarayan
10y ago
Can you share a "behind the scenes" of what it took to get Distill off the ground? You hint at dotting your "i"s and crossing your "t"s, but an explicit manual would be useful. Other communities than just machi
80.
▲
by
arjunnarayan
10y ago
[Disclaimer: CockroachDB engineer here, working on performance and benchmarking] IIRC, in the case that aphyr refers to for these specific numbers, the reads are scans that span multiple shards[1], while the writes are writes to single shar
81.
▲
by
arjunnarayan
10y ago
Minimum 3 nodes * node pricing of $.90/hour = 3 0.9 24*30 = 1944/month.
82.
▲
by
arjunnarayan
10y ago
It's just a rule of thumb as to what long run P/E ratios look like in the equity markets.
83.
▲
by
arjunnarayan
10y ago
He wanted a Tesla!
84.
▲
by
arjunnarayan
10y ago
I am not the GP, and I do not endorse the argument therein, but some evidence for some of his/her claims are provided by this article[1] by Daron Acemoglu, James Robinson and Thierry Verdier. I think Acemoglu and Robinson are the forem
85.
▲
by
arjunnarayan
10y ago
This probably isn't something that appeals to the Hacker News community in general, but the first thing that comes to mind is large scale art projects, of the sort that take weeks/months to prepare (such as the big Burning Man ins
86.
▲
by
arjunnarayan
10y ago
"Another aspect of blockchain, as I often emphasize, is sociological: Blockchains are cool. If you announce that you are updating the database software used by a consortium of banks to track derivatives trades, the New York Times will
87.
▲
by
arjunnarayan
10y ago
Yes, I agree with you. I'm replying specifically to the parent comment that says dual class stock is a 'racket'.
88.
▲
by
arjunnarayan
10y ago
Nobody forced you to buy Facebook shares. The stock classes were disclosed at IPO. These were the terms. If you want to buy into a company and have control, buy some other company's stock.
89.
▲
by
arjunnarayan
10y ago
You might want to read General Mattis on being too busy to read from when he was in the Marines: http://www.strifeblog.org/2013/05/07/with-rifle-and-bibliogr...
90.
▲
by
arjunnarayan
10y ago
Thank you for both these comments, this is the best explanation I've ever read about Searle (Searle is usually a punchline in my conversations with my friends[1]). I'm not completely convinced, and I think an effective rebuttal is
More ›