{"blog_url":"https://crumbjp.hateblo.jp/","provider_url":"https://hatena.blog","version":"1.0","html":"<iframe src=\"https://hatenablog-parts.com/embed?url=https%3A%2F%2Fcrumbjp.hateblo.jp%2Fentry%2F20130405%2F1365136897\" title=\" Analyze the Analyzer (MongoDB 2.4) - \u4e2d\u5e74engineer\u306e\u72ec\u308a\u8a00 - crumbjp\" class=\"embed-card embed-blogcard\" scrolling=\"no\" frameborder=\"0\" style=\"display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;\"></iframe>","url":"https://crumbjp.hateblo.jp/entry/20130405/1365136897","title":" Analyze the Analyzer (MongoDB 2.4)","image_url":null,"author_url":"https://blog.hatena.ne.jp/hiroppon/","type":"rich","published":"2013-04-05 13:41:37","provider_name":"Hatena Blog","author_name":"hiroppon","width":"100%","blog_title":"\u4e2d\u5e74engineer\u306e\u72ec\u308a\u8a00 - crumbjp","height":"190","description":"Analyzer problem ? MongoDB Analyzer sometimes retuns below values that is difficult to interpret. RS:PRIMARY> db.serverStatus().mem { \"bits\" : 64, \"resident\" : 127, \"virtual\" : 11292, \"supported\" : true, \"mapped\" : 5262, \"mappedWithJournal\" : 10524 } RS:PRIMARY> db.serverStatus({workingSet:1}).worki\u2026","categories":["mongodb"]}