Your idx miss % is low which means your index is in RAM but you are page faulting - your data it being faulted in from disk because you have such a small ram. Does the log show any slow queries?
On Friday, November 16, 2012 8:55:18 PM UTC, Nick Hoffman wrote:
> Hi guys. Considering the following info, is a server with 1GB of RAM and 2 > Xeon 2.13GHz CPUs sufficient? I ask because the CPU is spiking frequently.
On Friday, 16 November 2012 17:35:14 UTC-5, gregor wrote:
> Your idx miss % is low which means your index is in RAM but you are page > faulting - your data it being faulted in from disk because you have such a > small ram. > Does the log show any slow queries?
> On Friday, November 16, 2012 8:55:18 PM UTC, Nick Hoffman wrote:
>> Hi guys. Considering the following info, is a server with 1GB of RAM and >> 2 Xeon 2.13GHz CPUs sufficient? I ask because the CPU is spiking frequently.
On Friday, November 16, 2012 10:43:37 PM UTC, Nick Hoffman wrote:
> Hi gregor. I'm tracking slow queries in ScoutApp.com , which says that > MongoDB's averaging 6.6 slow queries per minute, which is pretty low.
> On Friday, 16 November 2012 17:35:14 UTC-5, gregor wrote:
>> Your idx miss % is low which means your index is in RAM but you are page >> faulting - your data it being faulted in from disk because you have such a >> small ram. >> Does the log show any slow queries?
>> On Friday, November 16, 2012 8:55:18 PM UTC, Nick Hoffman wrote:
>>> Hi guys. Considering the following info, is a server with 1GB of RAM and >>> 2 Xeon 2.13GHz CPUs sufficient? I ask because the CPU is spiking frequently.
On Friday, November 16, 2012 8:55:18 PM UTC, Nick Hoffman wrote:
> Hi guys. Considering the following info, is a server with 1GB of RAM and 2 > Xeon 2.13GHz CPUs sufficient? I ask because the CPU is spiking frequently.