Assertion Contradicted AI assessment confidence: 92% certainty 4/5 debate potential 3/5

Eric Frenkiel criticizes MongoDB for relying on a global write lock

Eric (MemSQL) · Panel discussion // Data Driven NYC #13 // Dec 2012 · Dec 5, 2013 · at 35:15

Eric Frenkiel, co-founder of MemSQL, explains the architectural limitations of MongoDB when compared to relational databases in high-concurrency environments.

0:00 / 0:05exact quote · 5.2s

▶ Watch the full episode on YouTube → 720p mp4 · rendered on demand · StarZero watermark

“Mongo also has a global write lock. So one writer will block everyone else until it completes.”

quote is from the automated transcript, cleaned for reading: filler sounds and stutters are removed, nothing is rephrased. names can be misheard (the analysis reads context, assessments check outside sources). how →

The claim, plainly

MongoDB utilizes a global write lock where a single writer blocks all other operations until completion.

a quote alone can be ambiguous, so this restates it with the references and context of the conversation around it resolved. AI-written; the tape below the player is the source.

Assessment

The claim is false on two distinct grounds. First, at the time of the statement in December 2013, MongoDB no longer utilized a global instance lock; MongoDB 2.2 (released in August 2012) replaced the global lock with per-database locking. Second, even in pre-2.2 releases that used an instance-wide lock, MongoDB implemented write lock yielding during disk I/O, meaning a writer did not block all other operations continuously until completion.

Official MongoDB 2.2 documentation states that beginning in August 2012, locking was implemented per-database rather than globally per mongod instance.
Pre-2.2 MongoDB documentation shows write operations yielded their lock when requiring disk I/O rather than holding it until full completion.

Checked against

[1] stackexchange.com [2] a-data-driven-guy.com [3] mongodb.org [4] mongoing.com [5] mongodb.com [6] practical-mongodb-aggregations.com

MongoDB release notes 2.2 database level lock 2012 "yield the write lock" "MongoDB" 2012 OR 2011 OR 2010 "Before 2.2, there is only one" "global" "lock per mongod instance" mongodb "MongoDB 2.0" release date 2011 "MongoDB 2.2" release date 2012

assessed as of 2026-07-31

This assessment is an AI reading of a public statement, made against the cited references with the confidence shown. It can be wrong. The quote, the tape and the references are all on this page; if something is off, use report an error below. full disclaimer →

Mentioned

MemSQL MongoDB

⚑ Spot an error? Report it

More from Eric (MemSQL)

Opinion

MemSQL's Eric Frenkiel: Open source is a marketing channel, not business model

“I think open source is, is fantastic. It's a great marketing channel. I don't think it's a great business model.”

Eric (MemSQL) Dec 5, 2013 ▶ 10:57 Panel discussion // Data Driven NYC #13 // Dec 2012

Insight

MemSQL's Eric Frenkiel argues analytics cannot be performed in key-value stores

“I mean I think, I mean, it's, you can't do analytics in key value.”

Eric (MemSQL) Dec 5, 2013 ▶ 13:29 Panel discussion // Data Driven NYC #13 // Dec 2012

Assertion Not checkable as stated

MemSQL's Eric Frenkiel argues on-premise infrastructure costs a fraction of AWS EC2

“I have a lot of you know, folks that spend tens of thousands of dollars a month on EC-II and they could do it for a fraction of the price if they did it on premise.”

Eric (MemSQL) Dec 5, 2013 ▶ 17:26 Panel discussion // Data Driven NYC #13 // Dec 2012

Assertion Partly supported

Frenkiel: MemSQL on EC2 achieves 1ms latency vs 60ms for MySQL

“Whenever you go with MM-SQL on EC-II, for example, you will see, like, one millisecond response times, and a Postgres or a MySQL is on the order of 60.”

Eric (MemSQL) Dec 5, 2013 ▶ 18:26 Panel discussion // Data Driven NYC #13 // Dec 2012

What-if

Eric Frenkiel: MemSQL would not exist if launched as an open-source project

“Fundamentally I don't think MemSQL would exist if we had to go into it the open source way.”

Eric (MemSQL) Dec 5, 2013 ▶ 11:34 Panel discussion // Data Driven NYC #13 // Dec 2012

Insight

Eric Frenkiel: Writing a lightweight parser is easier than unstructured analysis

“What we typically see with unstructured data is it's far easier to write a lightweight parser around that log file, for example, and get it structured very readily.”

Eric (MemSQL) Dec 5, 2013 ▶ 20:49 Panel discussion // Data Driven NYC #13 // Dec 2012

Eric Frenkiel criticizes MongoDB for relying on a global write lock

More from Eric (MemSQL)

Turn any episode into a week of clips.