posted on Sunday, May 22, 2005 11:10 PM
by
bradley
Allocated memory alert ... one more time
Alert on DOMAIN at 5/13/2005 8:29:05 PM
A large amount of memory is committed to applications and processes.
Consistently high memory usage can cause performance problems.
To determine which processes and applications are using the most memory, use
Task Manager. Monitor the activity of these resources over a few days. If they
continue to use a high level of memory and are less critical processes or
services, try stopping and then restarting them.
You can disable this alert or change its threshold by using the Change Alert
Notifications task in the Server Management Monitoring and Reporting taskpad.
So when I installed ISA 2004, I now have my allocated memory alert being thrown off by the MSDE instance tied to ISA server 2004.
So... how do I know this? Because my task manager told me so....and every night at exactly 8:30 p.m. I would get paged with a stupid allocated memory alert error [yeah I have critical alerts sent to my cell phone as alerts]. As you can see that Commit charge is running a bit “hot“ in my book, especially since before ISA 2004, it was certainly not running that much of memory.
That commit charge is running a bit hot again... so the first thing I do is look at what services are 'yanking' the memory again.
First we fire up task manager and we see that our friend, store.exe is our main memory 'sucker' and is normal, but that one right underneath ...we need to see what it is. We previously adjusted the task manager view [click view] to edit to show the PID, now we need to fire up the task services to double check.
Okay, so what does tasklist /svc from a command prompt tell us?
Ah ha...it's our Firewall monitoring service ....see that MSSQL$MSFW? That's our ISA server monitoring that indeed needs to be throttled.
If you've checked out the instructions on the SBS 2003 sp1 document [the community one, not the official one], you'll know that the recommendation is to perform a command to throttle that instance. So we open a command prompt and do the following:
Open a command prompt and type in the following instructions:
- Osql –E –S %computername%\MSFW
- sp_configure ‘show advanced options’,1
- reconfigure with override
- go
- sp_configure ‘max server memory’,NNNN (Where NNNN is the amount of ram in mb. Recommended amount is 100 MB for SBS)
- reconfigure with override
- go
and end the command with
As you can see the commit charge has now gone way down.
And you can see that PID 1612 [our firewall monitoring msde instance] is no longer sucking that memory.
And I'm once again a happy camper... along with my SBS box.