Presentation for Kuala Lumpur MongoDB User Group 4 @Laulima - Dec 7, 2011. Attempted to use DTrace to understand the behavior of GridFS under normal vs memory pressure condition. Discussion later on observed behavior.
for MongoDB • GridFS Under Normal Condition • GridFS Under Memory Pressure • Discussion • Bonus: DTrace Visualization of MongoPress • Bonus2: More DTrace Analytics/Visualization
and MongoDB :) • Disclaimer: Content includes mash-up of other DTrace Content from Joyent/Sun/Oracle folks • http://www.reddit.com/r/programming/comments/m2b2b/dont_use_mongodb/ “ But if you're intending to really run a large scale system on Mongo, one that a business might depend on, simply put: Don't. ”
until Measured and Tested • Setup: MongoDB-latest in zone setup as per Joyent • Setup: VirtualBox – 2 vCPU, 1GB, Joyent SmartOS • Setup: Default values; no tuning at all • Setup: File sizes tested: 100KB, 1MB, 5MB, 25MB, 50MB, 75MB, 90MB, 100MB, 500MB
Collect timestamps and other info (workload specifics) • Lets you create ideal metrics that matter and clear the FUD! • Imagine: • Black/white answers: either there is an issue, or there isn’t • 100% reliability • No expert interpretation required • No time consuming analysis required
dynamic (and static) probes • Includes a rich set of actions, including data aggregations • Currently for: • Solaris-based OSes (SmartOS, OpenIndiana, Solaris 10+ etc.) • Mac OS X 10.5+, FreeBSD 7.1+ • < Alpha - Oracle Unbreakable Linux, Linux? http://crtags.blogspot.com • Production safe; in use since 2005 • User- and kernel-land tracing • C & awk inspired language (D-language)
cases • Observation: mmap calls dispersed with large gaps between - why? • Observation: Memory Hungry; suck up all available – how to limit? • Observation: Diskspace Hungry; suck up all available – how to compress/dedupe? • Others?