Top all-time · #4488
Yoshinori Matsunobu
Personal blog · yoshinorimatsunobu.blogspot.comprogrammingdatasystems
Yoshinori Matsunobu's personal blog at yoshinorimatsunobu.blogspot.com covers programming, data and systems. Since 2010, 17 different Hacker News readers have linked it 17 times, most often “Using MySQL as a NoSQL - A story for exceeding 750,000 qps on a commodity server”. The last post was in 2017, but the archive is still widely read.
Too few sampled comments (9) to say how often HN recommends it.?
Why HN links it
HN readers link Yoshinori Matsunobu's blog for technical write-ups on MySQL/InnoDB performance and HandlerSocket as a NoSQL-style interface. Commenters cite it as a more balanced or illuminating take than other benchmarks.
Summarised by Claude from a sample of 9 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- Using MySQL as a NoSQL - A story for exceeding 750,000 qps on a commodity server9 people · 9 mentions · first linked 2010-10-19
- Why buffered writes are sometimes stalled2 people · 2 mentions · first linked 2014-12-15
What Hacker News says?
One of those companies is facebook right? I think this blog post provides a much more balanced view: http://yoshinorimatsunobu.blogspot.com/2017/11/towards-bigge...
Comment linking /2017/11/towards-bigger-small-data.html
on “Postgres scaling advice”Submitted Using MySQL as a NoSQL - A story for exceeding 750,000 qps on a commodity server as a story · 169 points
HN discussionThose benchmarks are very flawed as HandlerSocket only works in InnoDB. This is a better post on the subject: http://yoshinorimatsunobu.blogspot.com/2010/10/using-mysql-a...
Comment linking /2010/10/using-mysql-as-nosql-story-for.html
on “The key value store we ignored (Postgresql)”Submitted Using MySQL as a NoSQL - A story for exceeding 750,000 qps on a commodity server as a story · 112 points
HN discussionHandlerSocket is an interesting approach to turn MySQL into a NoSQL database and get 700,000 requests per second on a single node. http://yoshinorimatsunobu.blogspot.com/2010/10/using-mysql-a... When I benchmarked Redis on an Intel hexacore I got 800,000 requests a second on 8 terminal windows. So I assume the MYSQL data fit in RAM.
Comment linking /2010/10/using-mysql-as-nosql-story-for.html?m=1
on “One million queries per second with MySQL”Submitted Making full table scan 10x faster in InnoDB as a story · 98 points
HN discussionThe OP video describes a FS based on Innodb and MySQL. It gets relatively poor performance (7-9X slower for common FS ops). However, the killer FS ops for a DB are subtree operations - 'rm -rf', 'chown -R', 'chmod -R'. In research in this field, these are the operations that get less limelight but are most important for a working system. I hazard a guess that the above implementation could still be made many times f…
Comment linking /2010/10/using-mysql-as-nosql-story-for.html
on “Database as Filesystem [video]”Submitted Why buffered writes are sometimes stalled as a story · 69 points
HN discussionPercona Server has lots of improvements (some small things and others that are pretty essential for me) On the SSD front, the main ones are: * You can put the innodb doublewrite buffer on your spinning disks - that's the best place for it since it's heavy sequential writes. See section 2.2.2 here http://yoshinorimatsunobu.blogspot.com/2009/05/tables-on-ssd... * The ability to tune various parts of innodb that were o…
Comment linking /2009/05/tables-on-ssd-redobinlogsystem.html
on “RIP Open Source MySQL”Submitted Using MySQL as NoSQL Store as a story · 63 points
HN discussionUnfortunately, it's not that easy. Don't forget about the impact of SQL parsing and connection costs. Here is a very illuminating post about it: http://yoshinorimatsunobu.blogspot.com/2010/10/using-mysql-a... The authors created a MySQL plugin that served as a network server and hooked into InnoDB without SQL parsing overhead. It also avoided the cost of opening/closing tables by keeping them open. According to thei…
Comment linking /2010/10/using-mysql-as-nosql-story-for.html
on “You Got NoSQL in MySQL: Memcached Plugin in MySQL Technology Preview”Submitted A New Take on MySQL Master High Availability as a story · 6 points
HN discussionThere was a more detailed discussion about HandlerSocket in another thread: http://news.ycombinator.com/item?id=1886137 Original article: http://yoshinorimatsunobu.blogspot.com/2010/10/using-mysql-a...
Comment linking /2010/10/using-mysql-as-nosql-story-for.html
on “InnoDB faster than NoSQL solutions?”Submitted Why buffered writes are sometimes stalled as a story · 2 points
HN discussionInnoDB provides a schemaless datastore and can be used directly. A couple of results for a quick google search for "innodb nosql": http://yoshinorimatsunobu.blogspot.com/2010/10/using-mysql-a... http://blogs.innodb.com/wp/2011/04/nosql-to-innodb-with-memc...
Comment linking /2010/10/using-mysql-as-nosql-story-for.html
on “Ask HN: Open Source project using MySQL as a schemaless datastore”Submitted Another reason to disable MySQL performance schema as a story · 1 points
HN discussionHaving now been exposed to both... If you ever want to use it as a caching system ... solr is the way to go. I personally think very highly of Sphinx, yet be aware that Sphinx will return ids not "content". When handlesocket was announced [1], for me the gem other than the obvious was this nugget of information. "No duplicate cache When you use memcached to cache MySQL/InnoDB records, records are cached in both memc…
Comment linking /2010/10/using-mysql-as-nosql-story-for.html
on “Ask HN: It's 2011 Sphinx or Solr?”
