--
You received this message because you are subscribed to the Google Groups "mongodb-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-dev+unsubscribe@googlegroups.com.
To post to this group, send email to mongo...@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-dev/457b6df4-0ded-415e-b497-fd336ea2a4eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
The performance counter queries are likely the default once-per-second diagnostic data collection. You can disable this using the diagnosticDataCollectionEnabled parameter. I don't believe querying the journal directory is related to diagnostic data collection though, and the timestamps on the screenshot you provided support that it is unrelated, as they are offset from the perf counter activity by about 0.6 seconds. What impact on CPU utilization do you see if you disable diagnostic data collection?Thanks,
Bruce
On Fri, Jun 16, 2017 at 1:09 AM, Prasanna V. Loganathar <p...@prasannavl.com> wrote:
Hi,
It seems that when MongoDB is idling on simply on a system, it uses a 1 second timer that constantly queries the journal directory, and also a the performance counter query keys. Haven't looked at the source code, yet, but wonder why it keeps doing that.While of course, this is in no way priority since it doesn't matter on servers, I constantly use MongoDB as a personal data store on my systems, and it uses a low, but constant CPU time, which bothers me while on portable devices (Of course, that's not MongoDB's ideal host). I keep having to turn the service on and off, when I need it. The other thing that's evident is the "metrics.interim.temp" that's consolidated into the diagnostic data every 10 seconds - which is rather okay. But querying the performance counters and the journal directory every second for no reason bother me a bit.
While it's obviously not the ideal host, let's take a look at how Microsoft handles the scenarios for instance - MSSQL Server (Express, LocalDB, or full instance) doesn't use any CPU (or occasional, if any) at all when idling, which makes it perfect for use on personal devices. Hoping to understand a little more if this is indeed a necessity, and/or is there any way make MongoDB idle without using system resources.Would be great if a Windows dev could shine some light on this.
--
You received this message because you are subscribed to the Google Groups "mongodb-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-dev...@googlegroups.com.