(This thread originated on oae-core, but is really meant for oae-dev.) If Mongo really has a global write lock [1] then it's got much the same problem that caused us to migrate away from Jackrabbit...
Snip: "Global write lock - MongoDB (as of the current version at the time of writing: 2.0), has a process-wide write lock. Conceptually this makes no sense. A write on collection X blocks a write on collection Y, despite MongoDB having no concept of transactions or join semantics. We reached practical limitations of MongoDB when pushing a mere 200 updates per second to a single server. At this point, all other operations including reads are blocked because of the write lock. When reaching out to 10gen for assistance, they recommended we look into sharding, since that is their general scaling solution." [1] http://blog.engineering.kiip.me/post/20988881092/a-year-with-mongodb -chris On 6/6/12 8:46 AM, Zach A. Thomas wrote: > This link may have circulated already, but it's relevant here: > http://blog.engineering.kiip.me/post/20988881092/a-year-with-mongodb > > There's nothing like cold reality to blunt a fellow's enthusiasm! > > Zach > On Jun 6, 2012, at 10:36 AM, Ray Davis wrote: > >> I wonder what his team switched to? PostgreSQL is the fallback I've seen >> most often. >> >> Best, >> Ray >> >> On 6/6/12 8:29 AM, Lance Speelmon wrote: >>> FYI - might be a useful data point… >>> >>> http://www.zopyx.com/blog/goodbye-mongodb >>> _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
