Large unmapped virtual memory usage for mongoDB when using rockmongo

[rspijker]

I noticed a large increase of non-mapped virtual memory when using rockmongo (up to about 150GB) and launched a private ticket about this with 10gen. They investigated and found a lot of eval() calls in the code were the cause. For server-side js a V8 js engine is fired up, which requires quite a bit of memory.

This kind of call should be avoided, especially since they can easily be replaced by native driver functions.

[bridgetkromhout]

I found this issue when investigating very high non-mapped virtual memory on one of our mongo servers. Since we are connecting rockmongo to an instance running a mongos process, a workaround for us is to restart that mongos process after using rockmongo. (Certainly this is preferable to restarting mongod.)

[daryltucker]

rockmongo uses a lot of eval(), I hear.

[stefanocudini]

Vote on this issue please #133