Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jiryu
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
jiryu
1y ago
That's a really cool technique oggy, I don't think I've heard of anything exactly like it. If you haven't told the TLA+ community about it yet, I'm sure they'd like to learn about your approach, either on the m
2.
▲
by
jiryu
5y ago
I gave the presentation in the linked article, here's a written version of the presentation: https://emptysqua.re/blog/paxos-vs-raft/ I hope that the "Paxos vs Raft" debate can die down, now that en
3.
▲
by
jiryu
9y ago
"Avoid instant messaging at all costs" is definitely good advice. I usually forget to take three breaths before answering there, but I usually remember before I answer an email. Plus, I have GMail's "undo send" feat
4.
▲
How I've failed and succeeded mentoring young coders
(emptysqua.re)
1 points
by
jiryu
12y ago
|
0 comments
5.
▲
I fooled myself into thinking my code was 8x faster. Learning from failure.
(emptysqua.re)
1 points
by
jiryu
12y ago
|
0 comments
6.
▲
by
jiryu
13y ago
MongoDB, Inc. in New York City, Palo Alto, and worldwide. H1B welcome. We make the open-source document database. Virtually all the software we make is open source. We solve very hard problems using C++, C, Java, Python, and a half-dozen ot
7.
▲
New MongoDB feature for efficiently paging geo queries
(emptysqua.re)
9 points
by
jiryu
13y ago
|
1 comments
8.
▲
by
jiryu
14y ago
w00t!
9.
▲
by
jiryu
14y ago
No - it can only use one for a given query. But a compound index like the ones I describe in the post can index many fields.
10.
▲
Optimizing MongoDB Compound Indexes
(emptysquare.net)
46 points
by
jiryu
14y ago
|
11 comments
11.
▲
by
jiryu
14y ago
None, almost certainly -- if you have enough RAM to fit your working data set, then MongoDB's writes are just changing memory. If it does need to read data from disk before changing it, the new yielding architecture that others have menti
12.
▲
by
jiryu
14y ago
One of the reasons DB-level locking is actually quite important is that the replication oplog is on the 'local' database and your data is on other databases -- so your application is no longer fighting with replication for the write lock.
13.
▲
Refactoring Tornado Code With gen.engine
(emptysquare.net)
2 points
by
jiryu
14y ago
|
0 comments
14.
▲
How I Asynchronized a Synchronous Python Library
(emptysquare.net)
9 points
by
jiryu
14y ago
|
1 comments