MongoDB Service taking off -
Whenever the server has started the Monggoode service, its display and use of PF will have to be shot up to 3.5 9 GB, although it has good configuration (Server 2008, 4GB RAM) and the mongled 64 bit latest release (2.0.6) Is using. Please understand me about this.
Thanks
I'm not sure how much you know about MongoDB But Mongo uses memory map files to access data, which results in a large number of monogodes are displayed for the process. When using memory-mapped files, this is normal. The amount of mapped datafile is divided into virtual size parameters Is shown in and Asey bytes show how much data is being cached in RAM. Bigger your data files, the maximum voxize of the Mongode process
If other processes require more RAM, then the virtual memory manager of the operating system will discard some memory from the cache and the bytes remaining on the monogode process will be left.
It is recommended to use a certain pagefile size. If you use a dynamic page file, then the OS does not increase it rapidly to keep the mapped memory calls private. Specifically a special warning is open to add if the page file is dynamic or (minimized) is very small set.
This explains how using MoronD works on MongoDB.
Here are some tools that show how you can diagnose system problems with mangodibi -
To be honest, I advise to proceed with this problem and during the problem, with Mangostat output as well as posting your problem here, along with the information it is now longer discussion Will be.
Comments
Post a Comment