Viewing profile — midom
midom
HN member- Joined
- Sat, Jul 09, 2011, 5:45 PM UTC
- HN karma
- 48
- Public activity
- 24 items
- HN profile
- View on Hacker News ↗
About midom
facebook, ex-wikipedia, ex-sun/mysql, ex-delfi/microlink
Recent public activity
-
comment
Comment #35643510
rocksdb is used in many more systems, but the storage layer behind TAO (UDB) is using MyRocks for quite a few years by now - migration was done in 2016 or so - https://engineering.…
-
comment
Comment #35643469
/wave
-
comment
Comment #35643464
https://developers.facebook.com/videos/f8-2018/cassandra-on-... (there's not much Cassandra now, though)
-
comment
Comment #35643417
something doesn't make sense here - MySQL/InnoDB does put tables into files, but partitions get separate file. MyRocks has a collection of files per each column family, and when yo…
-
comment
Comment #35643364
this misses multiple points - lots of block access happens via internal caches (hyperclock/lru/etc) and filesystem isn't in the critical path as much as you'd think. files are mapp…
-
comment
Comment #29486816
> Facebook has gone through many databases. Main use cases (social graph, messaging, ..) are on MySQL (and never left it). Storage engine is different, replication is improved, etc…
-
comment
Comment #29480880
I'm not sure page level compression can get efficiency of LSM-Tree, and frequent page writes will be a write amplification problem if you end up doing any form of copy-on-write and…
-
comment
Comment #29475634
¯\_(ツ)_/¯ optimizer guy says he did not do good job, shits on optimizer? There're many reasons to pick MySQL over PG at large scale deployments (economics, replication strategies, …
-
comment
Comment #27925339
there's also this team page, although it has been somewhat lower on volume lately - https://www.facebook.com/MySQLatFacebook/
-
comment
Comment #18811285
I can see some MySQL Infrastructure people in it :-)
-
comment
Comment #17403134
based on his previous submissions, he did not come here to discuss database technology or be factually correct.
-
comment
Comment #17403114
doesn't really qualify much as research - just lots of engineering to cover all corners
-
comment
Comment #17402638
+ app server / schema rework
-
comment
Comment #12167862
technically, it is a patch set, it gets frequently rebased against the upstream
- comment
-
comment
Comment #12167827
As long as you can shard (across multiple instances, or even within same instance, to avoid B-Tree latching), 1B+ rows within MySQL is piece of cake. Also, MySQL* is getting LSM-Tr…
-
comment
Comment #9989601
LIMIT 2 is also exposed to this issue, at different data ratios (in my tests up to LIMIT 142, I went through the math).
-
comment
Comment #9989598
So sad I can't see or reply to that comment anymore - I'm the author. Sorry, HN, my personal blog rarely gets that wide circulation, I should've done better job at introducing the …
-
comment
Comment #9351876
It was conversion from standard MongoDB to RocksDB based MongoDB, so replica count calculations don't really apply. And yes, Mongo did not optimize for space efficiency, which is w…
- comment
- story
-
comment
Comment #4163299
1, O_DIRECT, 1
-
comment
Comment #4163039
No, that is not the highest praise you can get from me. It definitely is very interesting technology, and what it does well, it does really well - though I didn't get to benchmark …
-
comment
Comment #2746059
oh well, maybe indeed I assumed more about general knowledge of new database technologies around. voltdb (Stonebraker's solution) is in-memory store, so are few other of all this n…