title

MongoDB Blog

text:Disqus Shortname

mongodbblog

Content-Type

text/html; charset=UTF-8

X-UA-Compatible

IE=edge,chrome=1

description

MongoDB Blog

og:title

MongoDB.org Community Blog

og:url

https://web.archive.org/web/20150403003336/http://blog.mongodb.org/

og:image

https://web.archive.org/web/20150403003336im_/https://media.mongodb.org/ico/icon-leaf.png

og:image

https://web.archive.org/web/20150403003336im_/http://24.media.tumblr.com/avatar_7d391eb913cd_128.png

og:image:secure_url

http://24.media.tumblr.com/avatar_7d391eb913cd_128.png

twitter:card

summary

twitter:description

32-bit MongoDB processes are limited to about 2 gb of data.  This has come as a surprise to a lot of people who are used to not having to worry about that.  The reason for this is that the MongoDB storage engine uses memory-mapped files for performance. By not supporting more than 2gb on 32-bit, we’ve been able to keep our code much simpler and cleaner.  This greatly reduces the number of bugs, and reduces the time that we need to release a 1.0 product. The world is moving toward all 64-bit very quickly.  Right now there aren’t too many people for whom 64-bit is a problem, and in the long term, we think this will be a non-issue.

twitter:title

32-bit limitations

twitter:url

https://web.archive.org/web/20150403003336im_/http://blog.mongodb.org/post/137788967/32-bit-limitations

twitter:site

tumblr

alternate

https://web.archive.org/web/20150403003336/android-app://com.tumblr/tumblr/x-callback-url/blog?blogName=mongodb%26postID=137788967

alternate

https://web.archive.org/web/20150403003336/http://www.tumblr.com/oembed/1.0?url=http://blog.mongodb.org/post/137788967/32-bit-limitations

icon

https://web.archive.org/web/20150403003336im_/http://mms.mongodb.com/static/images/favicon.ico

shortcut icon

https://web.archive.org/web/20150403003336im_/http://media.mongodb.org.s3.amazonaws.com/ico/favicon.ico

stylesheet

https://web-static.archive.org/_static/css/banner-styles.css?v=1B2M2Y8A