In Resource Monitor on Windows 2008 R2, looking at the CPU tab, then selecting the dbsrv12.exe process and looking in Associated Handles list.
I see a entry, type "Event" and Handle Name "KernelObjectsMaximumCommitCondition" I am having performance problems with a DB and was poking around and found this.
http://msdn.microsoft.com/en-us/library/windows/hardware/ff563847(v=vs.85).aspx Says: "This event is set when the operating system's commit charge is near the maximum commit limit. In other words, memory usage is very high, very little space is available in physical memory or paging files, and the operating system cannot increase the size of its paging files. (A system administrator can always increase the size or number of paging files, without restarting the computer, if sufficient storage resources exist.) ... Each of these events are notification events. They remain set as long as the triggering condition remains true."
On the DB I am looking at this event has been present for hours now, ever since I noticed it. The server is virtual but it has 24gb of RAM (I think fully allocated to this instance) and a OS managed swap file with a lot of disk space to expand into if it needed to.
Does anyone have any thoughts?
asked 22 Sep '11, 12:21
The presence of the event is not critical it just tells you, that the process is listening to the event, e.g. you should see this event also for the explorer.exe. You have to look at the properties of the event to identify if it is also signaled. Only if it is signaled, the event (or the underlying condition) has really occured.
answered 23 Sep '11, 07:21