Guest Frank Posted June 10, 2008 Posted June 10, 2008 We have a Windows Server 2003 that has 4 Gb of memory installed. Windows recognizes the memory if I loop at the properties of the server. However the taskmanager shows only 200 MB free memory and all running programs use 200-300MB of memory. However virtual memory use is rather high. This is a SQL server and SQL server uses 77 MB of physical memory and 1.7 GB of virtual memory. Boot.ini looks like this: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, Standard" /noexecute=optout /fastdetect /PAE /3GB Only change in the last half year has been the move of the server to another 19"rack after which this problem occurred. Before that the server worked perfect. I had removed the switches /PAE and /3GB for testing but that did not work. Thanks in advance. Frank
Guest Justin Rich Posted June 10, 2008 Posted June 10, 2008 Re: Memory issue How does the memory look after a reboot? I assume these numbers were taken after an extended period of uptime? "Frank" <Frank@discussions.microsoft.com> wrote in message news:6B8669BB-EF1F-4D77-B471-487E108C15F6@microsoft.com... > We have a Windows Server 2003 that has 4 Gb of memory installed. Windows > recognizes the memory if I loop at the properties of the server. > > However the taskmanager shows only 200 MB free memory and all running > programs use 200-300MB of memory. However virtual memory use is rather > high. > This is a SQL server and SQL server uses 77 MB of physical memory and 1.7 > GB > of virtual memory. > > Boot.ini looks like this: > > [boot loader] > timeout=30 > default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS > [operating systems] > multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, > Standard" > /noexecute=optout /fastdetect /PAE /3GB > > Only change in the last half year has been the move of the server to > another > 19"rack after which this problem occurred. Before that the server worked > perfect. > > I had removed the switches /PAE and /3GB for testing but that did not > work. > > Thanks in advance. > > Frank
Guest Frank Posted June 10, 2008 Posted June 10, 2008 Re: Memory issue Hi Justin, This numbers are the same after a reboot. SQL server is configured to use a fixed amount of memory between 1.5 and 2.5 Gb and in the past this would result in the use of at least 1.7 Gb of physical memory, now it uses 1.7 Gb of virtual memory as there is almost no physical memory available. best regards, Frank "Justin Rich" wrote: > How does the memory look after a reboot? > I assume these numbers were taken after an extended period of uptime? > > "Frank" <Frank@discussions.microsoft.com> wrote in message > news:6B8669BB-EF1F-4D77-B471-487E108C15F6@microsoft.com... > > We have a Windows Server 2003 that has 4 Gb of memory installed. Windows > > recognizes the memory if I loop at the properties of the server. > > > > However the taskmanager shows only 200 MB free memory and all running > > programs use 200-300MB of memory. However virtual memory use is rather > > high. > > This is a SQL server and SQL server uses 77 MB of physical memory and 1.7 > > GB > > of virtual memory. > > > > Boot.ini looks like this: > > > > [boot loader] > > timeout=30 > > default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS > > [operating systems] > > multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, > > Standard" > > /noexecute=optout /fastdetect /PAE /3GB > > > > Only change in the last half year has been the move of the server to > > another > > 19"rack after which this problem occurred. Before that the server worked > > perfect. > > > > I had removed the switches /PAE and /3GB for testing but that did not > > work. > > > > Thanks in advance. > > > > Frank > > >
Guest Justin Rich Posted June 10, 2008 Posted June 10, 2008 Re: Memory issue I would suggest using the sysinternals procexp tool in order to dig in to your memory usage and see what is eating up all of your memory and go from there. also, if you could get a memory listing and post it here that would be useful. i think there is a sysinternals tool for that, but personally i would use powershell and do a get-process "Frank" <Frank@discussions.microsoft.com> wrote in message news:55CB144B-452D-4F5C-AB33-3B1C650FEB68@microsoft.com... > Hi Justin, > > This numbers are the same after a reboot. SQL server is configured to use > a > fixed amount of memory between 1.5 and 2.5 Gb and in the past this would > result in the use of at least 1.7 Gb of physical memory, now it uses 1.7 > Gb > of virtual memory as there is almost no physical memory available. > > best regards, > > Frank > > "Justin Rich" wrote: > >> How does the memory look after a reboot? >> I assume these numbers were taken after an extended period of uptime? >> >> "Frank" <Frank@discussions.microsoft.com> wrote in message >> news:6B8669BB-EF1F-4D77-B471-487E108C15F6@microsoft.com... >> > We have a Windows Server 2003 that has 4 Gb of memory installed. >> > Windows >> > recognizes the memory if I loop at the properties of the server. >> > >> > However the taskmanager shows only 200 MB free memory and all running >> > programs use 200-300MB of memory. However virtual memory use is rather >> > high. >> > This is a SQL server and SQL server uses 77 MB of physical memory and >> > 1.7 >> > GB >> > of virtual memory. >> > >> > Boot.ini looks like this: >> > >> > [boot loader] >> > timeout=30 >> > default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS >> > [operating systems] >> > multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, >> > Standard" >> > /noexecute=optout /fastdetect /PAE /3GB >> > >> > Only change in the last half year has been the move of the server to >> > another >> > 19"rack after which this problem occurred. Before that the server >> > worked >> > perfect. >> > >> > I had removed the switches /PAE and /3GB for testing but that did not >> > work. >> > >> > Thanks in advance. >> > >> > Frank >> >> >>
Guest Frank Posted June 11, 2008 Posted June 11, 2008 Re: Memory issue Hi Justin, I have used process explorer to investigate this problem but it seems that Windows is using about 512MB - 1 Gb of the available physical memory. All other memory is not showing up at all. Below is a list of all that is running and how much memory it is using according to pslist. Name Priv VM BackupClient 1636 36216 BackupClientService 10380 82164 BacsTray 896 32400 cmd 1476 13996 CNTAoSMgr 1132 21860 csrss 1888 29084 csrss 852 22944 ctfmon 596 26124 explorer 8332 74012 iexplore 26480 110500 inetinfo 3176 48360 logon.scr 344 14144 lsass 7508 42444 mqsvc 3404 38220 msdtc 1940 25448 mssearch 5632 34060 NTRtScan 13412 140472 PccNTMon 3196 45380 procexp 13592 58696 pslist 1000 27520 rdpclip 1068 32828 services 2008 50212 smss 132 3548 snmp 3928 42760 spoolsv 3892 29668 SQBCoreService 6976 66812 sqlagent 2624 43896 sqlmangr 1412 37516 sqlservr 77308 1787004 svchost 864 19424 svchost 1628 22716 svchost 3932 41256 svchost 4280 26072 svchost 18124 123176 svchost 576 17204 svchost 304 7232 svchost 2972 33852 svchost 2576 59396 System 0 1940 TmListen 10860 117584 TmPfw 1408 43840 TmProxy 1692 30676 winlogon 10876 62908 winlogon 1608 33508 wmiprvse 1844 27416 total: 269764 3686488 As you can see the total memory used is about 260Kb and there is around 200 kb free. However PSinfo shows this info: Processors: 2 Processor speed: 2.3 GHz Processor type: Intel® Xeon® CPU 5140 @ Physical memory: 4096 MB This is the weirdies thing I ever saw. Frank "Justin Rich" wrote: > I would suggest using the sysinternals procexp tool in order to dig in to > your memory usage and see what is eating up all of your memory and go from > there. > > also, if you could get a memory listing and post it here that would be > useful. i think there is a sysinternals tool for that, but personally i > would use powershell and do a get-process > > > "Frank" <Frank@discussions.microsoft.com> wrote in message > news:55CB144B-452D-4F5C-AB33-3B1C650FEB68@microsoft.com... > > Hi Justin, > > > > This numbers are the same after a reboot. SQL server is configured to use > > a > > fixed amount of memory between 1.5 and 2.5 Gb and in the past this would > > result in the use of at least 1.7 Gb of physical memory, now it uses 1.7 > > Gb > > of virtual memory as there is almost no physical memory available. > > > > best regards, > > > > Frank
Guest Justin Rich Posted June 11, 2008 Posted June 11, 2008 Re: Memory issue What you have listed is the Private Virtual memory (Priv) and Virtual Memory. you are seeing roughly 270MB (not KB) of priv and about 3.5GB of Virtual Memory. The working set (ws) values would be of use. Although the working set is not an exact representation of what is in physical ram, its pretty close. Also its important to keep in mind that "Virtual Memory" does not mean its not in physical ram. VM is the virtual address space that the application is aware of. Also i see that SQL is using 1.7GB which is about right for a standard 32 bit system. the odd part is you are using the /3GB switch so it should be a bit more. run this and let me see the results pslist -m based on what i've seen so far this looks pretty normal. the one thing you might want to take a look at is the SQL end of things. your 1.7GB of sql VM looks as though SQL is not configured correctly. 1.7 is the typical max you would see for a standard 32bit system without /3GB (1.7 being as close as i've seen sql get to the 2gb limit) you may want to get rid of the /3gb and just use the /pae and then configure sql to use awe http://support.microsoft.com/kb/274750 (might be a new article, but this seems to cover what you need) sp_configure 'show advanced options', 1 RECONFIGURE GO sp_configure 'awe enabled', 1 RECONFIGURE GO sp_configure 'max server memory', 2560 <-- use 2.5GB of ram RECONFIGURE GO i'll take a look at the new memory list, but i suspect you want to work on tuning SQL. Justin "Frank" <Frank@discussions.microsoft.com> wrote in message news:A220B593-C86B-4E73-BE33-D00A4A8D19DC@microsoft.com... > Hi Justin, > > I have used process explorer to investigate this problem but it seems that > Windows is using about 512MB - 1 Gb of the available physical memory. All > other memory is not showing up at all. > > Below is a list of all that is running and how much memory it is using > according to pslist. > > Name Priv VM > BackupClient 1636 36216 > BackupClientService 10380 82164 > BacsTray 896 32400 > cmd 1476 13996 > CNTAoSMgr 1132 21860 > csrss 1888 29084 > csrss 852 22944 > ctfmon 596 26124 > explorer 8332 74012 > iexplore 26480 110500 > inetinfo 3176 48360 > logon.scr 344 14144 > lsass 7508 42444 > mqsvc 3404 38220 > msdtc 1940 25448 > mssearch 5632 34060 > NTRtScan 13412 140472 > PccNTMon 3196 45380 > procexp 13592 58696 > pslist 1000 27520 > rdpclip 1068 32828 > services 2008 50212 > smss 132 3548 > snmp 3928 42760 > spoolsv 3892 29668 > SQBCoreService 6976 66812 > sqlagent 2624 43896 > sqlmangr 1412 37516 > sqlservr 77308 1787004 > svchost 864 19424 > svchost 1628 22716 > svchost 3932 41256 > svchost 4280 26072 > svchost 18124 123176 > svchost 576 17204 > svchost 304 7232 > svchost 2972 33852 > svchost 2576 59396 > System 0 1940 > TmListen 10860 117584 > TmPfw 1408 43840 > TmProxy 1692 30676 > winlogon 10876 62908 > winlogon 1608 33508 > wmiprvse 1844 27416 > > total: 269764 3686488 > > As you can see the total memory used is about 260Kb and there is around > 200 > kb free. > > However PSinfo shows this info: > > Processors: 2 > Processor speed: 2.3 GHz > Processor type: Intel® Xeon® CPU 5140 @ > Physical memory: 4096 MB > > This is the weirdies thing I ever saw. > > Frank > > "Justin Rich" wrote: > >> I would suggest using the sysinternals procexp tool in order to dig in to >> your memory usage and see what is eating up all of your memory and go >> from >> there. >> >> also, if you could get a memory listing and post it here that would be >> useful. i think there is a sysinternals tool for that, but personally i >> would use powershell and do a get-process >> >> >> "Frank" <Frank@discussions.microsoft.com> wrote in message >> news:55CB144B-452D-4F5C-AB33-3B1C650FEB68@microsoft.com... >> > Hi Justin, >> > >> > This numbers are the same after a reboot. SQL server is configured to >> > use >> > a >> > fixed amount of memory between 1.5 and 2.5 Gb and in the past this >> > would >> > result in the use of at least 1.7 Gb of physical memory, now it uses >> > 1.7 >> > Gb >> > of virtual memory as there is almost no physical memory available. >> > >> > best regards, >> > >> > Frank >
Guest Frank Posted June 11, 2008 Posted June 11, 2008 Re: Memory issue Hi Justin, Sorry for the mix up KB - MB. I meant MB. To start with the result of pslist -m Name Pid VM WS Priv Priv Pk Faults NonP Page Idle 0 0 28 0 0 0 0 0 System 4 1940 228 0 0 10759027 0 0 smss 288 3548 248 132 172 359 0 6 csrss 336 29200 2528 1892 3612 18004 5 75 winlogon 364 62908 5480 10876 13668 145423 51 101 services 412 49956 3840 1976 2060 70414 8 92 lsass 424 42444 4008 7544 7824 15870 14 56 svchost 640 19680 1096 888 944 2992 2 35 svchost 704 22204 2508 1584 1632 7102 20 40 svchost 768 41256 1580 3932 4000 7657 5 64 svchost 804 26072 2184 4280 4328 6261 6 39 svchost 820 169360 23508 24120 35276 365800 53 170 spoolsv 952 29924 3552 3940 4524 53473 4 44 msdtc 976 25448 520 1940 1988 1581 16 40 BackupClientService 1104 82164 7268 10380 21296 59046490 5 76 svchost 1180 17204 200 576 600 603 2 33 sqlservr 1252 1787020 33992 77384 78664 430705 173 107 svchost 1328 7232 200 304 332 388 1 15 snmp 1376 42760 1588 3928 4492 11500 7 65 SQBCoreService 1424 66812 1116 6976 33140 412501 5 67 mqsvc 1912 38220 288 3404 3620 2019 129 63 mssearch 1968 34060 440 5632 5656 3246 4 56 sqlagent 1528 43896 1704 2624 2932 14570 4 63 svchost 1656 33340 1208 2924 2972 1932 6 55 svchost 1420 59652 2004 2600 23148 7049 5 59 csrss 3060 22944 200 852 896 861 3 43 winlogon 3084 33508 376 1608 2612 2586 4 60 rdpclip 3216 33084 1608 1084 1100 3308 2 62 explorer 3316 74268 10136 8396 10608 9787780 10 125 BacsTray 3552 32400 608 896 908 2034 2 57 BackupClient 3580 36216 1300 1636 1760 9540 2 59 ctfmon 3612 26072 1876 596 896 10074 3 52 sqlmangr 3620 37516 1136 1412 2800 2611 3 66 wmiprvse 2524 27416 568 1844 2424 7816 3 45 logon.scr 304 14144 220 344 344 653 1 29 inetinfo 1004 48360 2012 3176 3376 8605 5 69 NTRtScan 3464 148664 15184 13536 14444 1465266 12 78 TmListen 1792 117584 9240 10872 14444 442991 43 102 PccNTMon 676 45380 4184 3204 4500 73452 5 71 TmPfw 1688 43840 1752 1408 2652 22065 5 65 CNTAoSMgr 3780 21860 552 1132 1144 1057 2 31 TmProxy 2728 30676 272 1692 4324 6801 34 37 cmd 4732 13996 704 1476 1532 646 1 27 wuauclt 4720 33960 3860 2012 2044 1119 3 63 wmiprvse 632 29332 5356 2240 2712 1452 3 47 pslist 5928 27520 2684 1000 1016 811 2 47 According to MS AWE should not be enabled on servers with 4 GB or less. However I have tried it and it did not solve the problem. > based on what i've seen so far this looks pretty normal. We have about 15 other DB servers and believe me this is not normal. Below is a listing of another DB server. Both servers have 4 Gb memory, and both have the /PAE and the /3Gb enabled. Name Pid VM WS Priv Priv Pk Faults NonP Page Idle 0 0 28 0 0 0 0 0 System 4 1940 240 0 0 12730350 0 0 smss 328 3548 480 128 168 371 0 6 csrss 376 29212 4748 1880 1988 8220 6 83 winlogon 404 60612 8284 9672 12332 100872 43 97 services 452 61212 24436 4304 12256 54017 13 107 lsass 464 50288 9196 8596 8664 6642 20 64 svchost 696 19420 2788 864 944 871 2 35 svchost 748 22116 3572 1376 1464 1157 20 39 svchost 812 43088 4660 3912 4028 3641 6 64 svchost 848 25772 5776 3752 3800 2081 6 39 svchost 864 149772 33392 25972 45392 2100416 55 167 spoolsv 996 29648 5912 4012 4520 12835 4 43 msdtc 1020 24540 4476 1868 1916 1214 5 38 BackupClientService 1156 73456 11544 7860 16192 59648100 5 76 cimntfy 1172 32236 3632 1116 1132 923 3 54 cissesrv 1196 7084 1424 260 284 53300 1 15 cpqrcmc 1208 7336 1324 280 284 329 1 15 vcagent 1224 32088 6996 2328 2496 1887 2 53 svchost 1256 17204 2224 576 600 600 2 33 inetinfo 1336 49312 8944 3376 5408 12618 5 69 sqlservr 1424 1833320 1783240 1745952 1746948 1321535 19 126 svchost 1568 13844 2624 936 936 1197 2 23 snmp 1596 56960 4372 10720 12880 27825 9 81 SQBCoreService 1656 67832 9708 6964 34428 316306 5 67 sysdown 1768 10608 1480 336 336 366 1 21 smhstart 1784 17408 3248 1344 1344 811 2 28 hpsmhd 1920 39504 11116 7468 7944 33429 246 66 cpqnimgt 2044 50688 6396 3484 4064 1629 4 70 cqmgserv 2100 36256 4976 3576 3576 866074 5 55 cqmgstor 2120 27864 4524 3704 3772 1164 7 47 mssearch 2144 34056 1300 4136 4168 1976 4 56 wmiprvse 2284 30548 6588 3100 4908 2950 3 45 svchost 2332 32480 7760 5020 6984 7952 5 39 rotatelogs 2500 20872 1940 620 620 494 1 40 rotatelogs 2508 20872 1916 612 612 488 1 40 hpsmhd 2552 105552 17224 14956 14968 37236 29 74 cqmghost 2680 42852 7052 3420 3640 9972022 6 66 rotatelogs 2720 20872 1948 620 620 496 1 40 rotatelogs 2728 20872 1924 612 612 490 1 40 sqlagent 2880 45432 3304 2684 2972 5495 5 63 svchost 4004 33596 4028 2956 3028 1082 6 55 svchost 1520 58372 4808 2596 23100 8265 5 59 wmiprvse 4316 46964 8488 4888 5368 308082 5 69 explorer 4936 74976 15992 7972 9648 9136526 11 128 cpqteam 5004 26064 2636 612 612 793 1 49 jusched 5016 38044 5836 1564 1584 1654 5 70 BackupClient 5032 37256 3020 1716 1820 4704 2 61 ctfmon 5052 17544 4608 528 896 1602 3 34 sqlmangr 5060 38556 5340 1464 2852 2393 3 67 csrss 4044 22940 2612 896 944 974 3 43 winlogon 4720 33508 5008 1660 1732 1688 4 60 rdpclip 5664 32828 3992 1040 1072 1322 2 61 logon.scr 5080 14144 1656 344 344 447 1 29 NTRtScan 4708 95236 16820 11680 12652 1264245 9 68 TmListen 4900 117660 17472 10264 12700 229087 43 102 PccNTMon 1028 47428 7880 3208 4504 35788 5 71 TmPfw 4884 43836 5420 1408 2636 11105 5 65 CNTAoSMgr 5676 21856 2652 1132 1144 685 2 31 TmProxy 5884 30676 5132 1452 2764 2914 34 37 w3wp 584 40276 6892 3604 3632 2835 7 45 wuauclt 2056 34468 3976 2044 2044 1137 3 63 IF you compare the SQLServer prcess you can see that on the "good" server the physical memory used is around 1.7 GB however on the "bad" server it is only 33 MB sqlservr 1424 1833320 1783240 1745952 1746948 1321535 19 126 sqlservr 1252 1787020 33992 77384 78664 430705 173 107 My guess is that SQL is not the problem here. If I shut down SQL server I only get around 33 MB back. Something is eating my physical memory and it is not showing up in any program or taskmanager. It could be a bug in Windows or there is a serious problem with my server hardware. best regards, Frank "Justin Rich" wrote: > What you have listed is the Private Virtual memory (Priv) and Virtual > Memory. you are seeing roughly 270MB (not KB) of priv and about 3.5GB of > Virtual Memory. > The working set (ws) values would be of use. Although the working set is not > an exact representation of what is in physical ram, its pretty close. > Also its important to keep in mind that "Virtual Memory" does not mean its > not in physical ram. VM is the virtual address space that the application is > aware of. > > Also i see that SQL is using 1.7GB which is about right for a standard 32 > bit system. the odd part is you are using the /3GB switch so it should be a > bit more. > run this and let me see the results > pslist -m > > based on what i've seen so far this looks pretty normal. the one thing you > might want to take a look at is the SQL end of things. your 1.7GB of sql VM > looks as though SQL is not configured correctly. 1.7 is the typical max you > would see for a standard 32bit system without /3GB (1.7 being as close as > i've seen sql get to the 2gb limit) > > you may want to get rid of the /3gb and just use the /pae and then configure > sql to use awe > http://support.microsoft.com/kb/274750 (might be a new article, but this > seems to cover what you need) > > sp_configure 'show advanced options', 1 > RECONFIGURE > GO > sp_configure 'awe enabled', 1 > RECONFIGURE > GO > sp_configure 'max server memory', 2560 <-- use 2.5GB of ram > RECONFIGURE > GO > > i'll take a look at the new memory list, but i suspect you want to work on > tuning SQL. > > Justin > > > "Frank" <Frank@discussions.microsoft.com> wrote in message > news:A220B593-C86B-4E73-BE33-D00A4A8D19DC@microsoft.com... > > Hi Justin, > > > > I have used process explorer to investigate this problem but it seems that > > Windows is using about 512MB - 1 Gb of the available physical memory. All > > other memory is not showing up at all. > > > > Below is a list of all that is running and how much memory it is using > > according to pslist. > > > > Name Priv VM > > BackupClient 1636 36216 > > BackupClientService 10380 82164 > > BacsTray 896 32400 > > cmd 1476 13996 > > CNTAoSMgr 1132 21860 > > csrss 1888 29084 > > csrss 852 22944 > > ctfmon 596 26124 > > explorer 8332 74012 > > iexplore 26480 110500 > > inetinfo 3176 48360 > > logon.scr 344 14144 > > lsass 7508 42444 > > mqsvc 3404 38220 > > msdtc 1940 25448 > > mssearch 5632 34060 > > NTRtScan 13412 140472 > > PccNTMon 3196 45380 > > procexp 13592 58696 > > pslist 1000 27520 > > rdpclip 1068 32828 > > services 2008 50212 > > smss 132 3548 > > snmp 3928 42760 > > spoolsv 3892 29668 > > SQBCoreService 6976 66812 > > sqlagent 2624 43896 > > sqlmangr 1412 37516 > > sqlservr 77308 1787004 > > svchost 864 19424 > > svchost 1628 22716 > > svchost 3932 41256 > > svchost 4280 26072 > > svchost 18124 123176 > > svchost 576 17204 > > svchost 304 7232 > > svchost 2972 33852 > > svchost 2576 59396 > > System 0 1940 > > TmListen 10860 117584 > > TmPfw 1408 43840 > > TmProxy 1692 30676 > > winlogon 10876 62908 > > winlogon 1608 33508 > > wmiprvse 1844 27416 > > > > total: 269764 3686488 > > > > As you can see the total memory used is about 260Kb and there is around > > 200 > > kb free. > > > > However PSinfo shows this info: > > > > Processors: 2 > > Processor speed: 2.3 GHz > > Processor type: Intel® Xeon® CPU 5140 @ > > Physical memory: 4096 MB > > > > This is the weirdies thing I ever saw. > > > > Frank > > > > "Justin Rich" wrote: > > > >> I would suggest using the sysinternals procexp tool in order to dig in to > >> your memory usage and see what is eating up all of your memory and go > >> from > >> there. > >> > >> also, if you could get a memory listing and post it here that would be > >> useful. i think there is a sysinternals tool for that, but personally i > >> would use powershell and do a get-process > >> > >> > >> "Frank" <Frank@discussions.microsoft.com> wrote in message > >> news:55CB144B-452D-4F5C-AB33-3B1C650FEB68@microsoft.com... > >> > Hi Justin, > >> > > >> > This numbers are the same after a reboot. SQL server is configured to > >> > use > >> > a > >> > fixed amount of memory between 1.5 and 2.5 Gb and in the past this > >> > would > >> > result in the use of at least 1.7 Gb of physical memory, now it uses > >> > 1.7 > >> > Gb > >> > of virtual memory as there is almost no physical memory available. > >> > > >> > best regards, > >> > > >> > Frank > > > > >
Guest Justin Rich Posted June 11, 2008 Posted June 11, 2008 Re: Memory issue yeah your working set is a bit on the tiny side... what does task manager say your system cache is taking? and total kernel memory? "Frank" <Frank@discussions.microsoft.com> wrote in message news:C9C4C7CA-58AD-4A9E-897C-6FCAA837008E@microsoft.com... > Hi Justin, > > Sorry for the mix up KB - MB. I meant MB. > > To start with the result of pslist -m > > Name Pid VM WS Priv Priv Pk Faults NonP > Page > Idle 0 0 28 0 0 0 0 > 0 > System 4 1940 228 0 0 10759027 0 > 0 > smss 288 3548 248 132 172 359 0 > 6 > csrss 336 29200 2528 1892 3612 18004 5 > 75 > winlogon 364 62908 5480 10876 13668 145423 51 > 101 > services 412 49956 3840 1976 2060 70414 8 > 92 > lsass 424 42444 4008 7544 7824 15870 14 > 56 > svchost 640 19680 1096 888 944 2992 2 > 35 > svchost 704 22204 2508 1584 1632 7102 20 > 40 > svchost 768 41256 1580 3932 4000 7657 5 > 64 > svchost 804 26072 2184 4280 4328 6261 6 > 39 > svchost 820 169360 23508 24120 35276 365800 53 > 170 > spoolsv 952 29924 3552 3940 4524 53473 4 > 44 > msdtc 976 25448 520 1940 1988 1581 16 > 40 > BackupClientService 1104 82164 7268 10380 21296 59046490 5 > 76 > svchost 1180 17204 200 576 600 603 2 > 33 > sqlservr 1252 1787020 33992 77384 78664 430705 173 > 107 > svchost 1328 7232 200 304 332 388 1 > 15 > snmp 1376 42760 1588 3928 4492 11500 7 > 65 > SQBCoreService 1424 66812 1116 6976 33140 412501 5 > 67 > mqsvc 1912 38220 288 3404 3620 2019 129 > 63 > mssearch 1968 34060 440 5632 5656 3246 4 > 56 > sqlagent 1528 43896 1704 2624 2932 14570 4 > 63 > svchost 1656 33340 1208 2924 2972 1932 6 > 55 > svchost 1420 59652 2004 2600 23148 7049 5 > 59 > csrss 3060 22944 200 852 896 861 3 > 43 > winlogon 3084 33508 376 1608 2612 2586 4 > 60 > rdpclip 3216 33084 1608 1084 1100 3308 2 > 62 > explorer 3316 74268 10136 8396 10608 9787780 10 > 125 > BacsTray 3552 32400 608 896 908 2034 2 > 57 > BackupClient 3580 36216 1300 1636 1760 9540 2 > 59 > ctfmon 3612 26072 1876 596 896 10074 3 > 52 > sqlmangr 3620 37516 1136 1412 2800 2611 3 > 66 > wmiprvse 2524 27416 568 1844 2424 7816 3 > 45 > logon.scr 304 14144 220 344 344 653 1 > 29 > inetinfo 1004 48360 2012 3176 3376 8605 5 > 69 > NTRtScan 3464 148664 15184 13536 14444 1465266 12 > 78 > TmListen 1792 117584 9240 10872 14444 442991 43 > 102 > PccNTMon 676 45380 4184 3204 4500 73452 5 > 71 > TmPfw 1688 43840 1752 1408 2652 22065 5 > 65 > CNTAoSMgr 3780 21860 552 1132 1144 1057 2 > 31 > TmProxy 2728 30676 272 1692 4324 6801 34 > 37 > cmd 4732 13996 704 1476 1532 646 1 > 27 > wuauclt 4720 33960 3860 2012 2044 1119 3 > 63 > wmiprvse 632 29332 5356 2240 2712 1452 3 > 47 > pslist 5928 27520 2684 1000 1016 811 2 > 47 > > According to MS AWE should not be enabled on servers with 4 GB or less. > However I have tried it and it did not solve the problem. > >> based on what i've seen so far this looks pretty normal. > > We have about 15 other DB servers and believe me this is not normal. Below > is a listing of another DB server. Both servers have 4 Gb memory, and both > have the /PAE and the /3Gb enabled. > > Name Pid VM WS Priv Priv Pk Faults NonP > Page > Idle 0 0 28 0 0 0 0 > 0 > System 4 1940 240 0 0 12730350 0 > 0 > smss 328 3548 480 128 168 371 0 > 6 > csrss 376 29212 4748 1880 1988 8220 6 > 83 > winlogon 404 60612 8284 9672 12332 100872 43 > 97 > services 452 61212 24436 4304 12256 54017 13 > 107 > lsass 464 50288 9196 8596 8664 6642 20 > 64 > svchost 696 19420 2788 864 944 871 2 > 35 > svchost 748 22116 3572 1376 1464 1157 20 > 39 > svchost 812 43088 4660 3912 4028 3641 6 > 64 > svchost 848 25772 5776 3752 3800 2081 6 > 39 > svchost 864 149772 33392 25972 45392 2100416 55 > 167 > spoolsv 996 29648 5912 4012 4520 12835 4 > 43 > msdtc 1020 24540 4476 1868 1916 1214 5 > 38 > BackupClientService 1156 73456 11544 7860 16192 59648100 5 > 76 > cimntfy 1172 32236 3632 1116 1132 923 3 > 54 > cissesrv 1196 7084 1424 260 284 53300 1 > 15 > cpqrcmc 1208 7336 1324 280 284 329 1 > 15 > vcagent 1224 32088 6996 2328 2496 1887 2 > 53 > svchost 1256 17204 2224 576 600 600 2 > 33 > inetinfo 1336 49312 8944 3376 5408 12618 5 > 69 > sqlservr 1424 1833320 1783240 1745952 1746948 1321535 19 > 126 > svchost 1568 13844 2624 936 936 1197 2 > 23 > snmp 1596 56960 4372 10720 12880 27825 9 > 81 > SQBCoreService 1656 67832 9708 6964 34428 316306 5 > 67 > sysdown 1768 10608 1480 336 336 366 1 > 21 > smhstart 1784 17408 3248 1344 1344 811 2 > 28 > hpsmhd 1920 39504 11116 7468 7944 33429 246 > 66 > cpqnimgt 2044 50688 6396 3484 4064 1629 4 > 70 > cqmgserv 2100 36256 4976 3576 3576 866074 5 > 55 > cqmgstor 2120 27864 4524 3704 3772 1164 7 > 47 > mssearch 2144 34056 1300 4136 4168 1976 4 > 56 > wmiprvse 2284 30548 6588 3100 4908 2950 3 > 45 > svchost 2332 32480 7760 5020 6984 7952 5 > 39 > rotatelogs 2500 20872 1940 620 620 494 1 > 40 > rotatelogs 2508 20872 1916 612 612 488 1 > 40 > hpsmhd 2552 105552 17224 14956 14968 37236 29 > 74 > cqmghost 2680 42852 7052 3420 3640 9972022 6 > 66 > rotatelogs 2720 20872 1948 620 620 496 1 > 40 > rotatelogs 2728 20872 1924 612 612 490 1 > 40 > sqlagent 2880 45432 3304 2684 2972 5495 5 > 63 > svchost 4004 33596 4028 2956 3028 1082 6 > 55 > svchost 1520 58372 4808 2596 23100 8265 5 > 59 > wmiprvse 4316 46964 8488 4888 5368 308082 5 > 69 > explorer 4936 74976 15992 7972 9648 9136526 11 > 128 > cpqteam 5004 26064 2636 612 612 793 1 > 49 > jusched 5016 38044 5836 1564 1584 1654 5 > 70 > BackupClient 5032 37256 3020 1716 1820 4704 2 > 61 > ctfmon 5052 17544 4608 528 896 1602 3 > 34 > sqlmangr 5060 38556 5340 1464 2852 2393 3 > 67 > csrss 4044 22940 2612 896 944 974 3 > 43 > winlogon 4720 33508 5008 1660 1732 1688 4 > 60 > rdpclip 5664 32828 3992 1040 1072 1322 2 > 61 > logon.scr 5080 14144 1656 344 344 447 1 > 29 > NTRtScan 4708 95236 16820 11680 12652 1264245 9 > 68 > TmListen 4900 117660 17472 10264 12700 229087 43 > 102 > PccNTMon 1028 47428 7880 3208 4504 35788 5 > 71 > TmPfw 4884 43836 5420 1408 2636 11105 5 > 65 > CNTAoSMgr 5676 21856 2652 1132 1144 685 2 > 31 > TmProxy 5884 30676 5132 1452 2764 2914 34 > 37 > w3wp 584 40276 6892 3604 3632 2835 7 > 45 > wuauclt 2056 34468 3976 2044 2044 1137 3 > 63 > > IF you compare the SQLServer prcess you can see that on the "good" server > the physical memory used is around 1.7 GB however on the "bad" server it > is > only 33 MB > > sqlservr 1424 1833320 1783240 1745952 1746948 1321535 19 > 126 > sqlservr 1252 1787020 33992 77384 78664 430705 > 173 107 > > My guess is that SQL is not the problem here. If I shut down SQL server I > only get around 33 MB back. Something is eating my physical memory and it > is > not showing up in any program or taskmanager. > > It could be a bug in Windows or there is a serious problem with my server > hardware. > > > best regards, > > Frank > > "Justin Rich" wrote: > >> What you have listed is the Private Virtual memory (Priv) and Virtual >> Memory. you are seeing roughly 270MB (not KB) of priv and about 3.5GB of >> Virtual Memory. >> The working set (ws) values would be of use. Although the working set is >> not >> an exact representation of what is in physical ram, its pretty close. >> Also its important to keep in mind that "Virtual Memory" does not mean >> its >> not in physical ram. VM is the virtual address space that the application >> is >> aware of. >> >> Also i see that SQL is using 1.7GB which is about right for a standard 32 >> bit system. the odd part is you are using the /3GB switch so it should be >> a >> bit more. >> run this and let me see the results >> pslist -m >> >> based on what i've seen so far this looks pretty normal. the one thing >> you >> might want to take a look at is the SQL end of things. your 1.7GB of sql >> VM >> looks as though SQL is not configured correctly. 1.7 is the typical max >> you >> would see for a standard 32bit system without /3GB (1.7 being as close as >> i've seen sql get to the 2gb limit) >> >> you may want to get rid of the /3gb and just use the /pae and then >> configure >> sql to use awe >> http://support.microsoft.com/kb/274750 (might be a new article, but this >> seems to cover what you need) >> >> sp_configure 'show advanced options', 1 >> RECONFIGURE >> GO >> sp_configure 'awe enabled', 1 >> RECONFIGURE >> GO >> sp_configure 'max server memory', 2560 <-- use 2.5GB of ram >> RECONFIGURE >> GO >> >> i'll take a look at the new memory list, but i suspect you want to work >> on >> tuning SQL. >> >> Justin >> >> >> "Frank" <Frank@discussions.microsoft.com> wrote in message >> news:A220B593-C86B-4E73-BE33-D00A4A8D19DC@microsoft.com... >> > Hi Justin, >> > >> > I have used process explorer to investigate this problem but it seems >> > that >> > Windows is using about 512MB - 1 Gb of the available physical memory. >> > All >> > other memory is not showing up at all. >> > >> > Below is a list of all that is running and how much memory it is using >> > according to pslist. >> > >> > Name Priv VM >> > BackupClient 1636 36216 >> > BackupClientService 10380 82164 >> > BacsTray 896 32400 >> > cmd 1476 13996 >> > CNTAoSMgr 1132 21860 >> > csrss 1888 29084 >> > csrss 852 22944 >> > ctfmon 596 26124 >> > explorer 8332 74012 >> > iexplore 26480 110500 >> > inetinfo 3176 48360 >> > logon.scr 344 14144 >> > lsass 7508 42444 >> > mqsvc 3404 38220 >> > msdtc 1940 25448 >> > mssearch 5632 34060 >> > NTRtScan 13412 140472 >> > PccNTMon 3196 45380 >> > procexp 13592 58696 >> > pslist 1000 27520 >> > rdpclip 1068 32828 >> > services 2008 50212 >> > smss 132 3548 >> > snmp 3928 42760 >> > spoolsv 3892 29668 >> > SQBCoreService 6976 66812 >> > sqlagent 2624 43896 >> > sqlmangr 1412 37516 >> > sqlservr 77308 1787004 >> > svchost 864 19424 >> > svchost 1628 22716 >> > svchost 3932 41256 >> > svchost 4280 26072 >> > svchost 18124 123176 >> > svchost 576 17204 >> > svchost 304 7232 >> > svchost 2972 33852 >> > svchost 2576 59396 >> > System 0 1940 >> > TmListen 10860 117584 >> > TmPfw 1408 43840 >> > TmProxy 1692 30676 >> > winlogon 10876 62908 >> > winlogon 1608 33508 >> > wmiprvse 1844 27416 >> > >> > total: 269764 3686488 >> > >> > As you can see the total memory used is about 260Kb and there is around >> > 200 >> > kb free. >> > >> > However PSinfo shows this info: >> > >> > Processors: 2 >> > Processor speed: 2.3 GHz >> > Processor type: Intel® Xeon® CPU 5140 @ >> > Physical memory: 4096 MB >> > >> > This is the weirdies thing I ever saw. >> > >> > Frank >> > >> > "Justin Rich" wrote: >> > >> >> I would suggest using the sysinternals procexp tool in order to dig in >> >> to >> >> your memory usage and see what is eating up all of your memory and go >> >> from >> >> there. >> >> >> >> also, if you could get a memory listing and post it here that would be >> >> useful. i think there is a sysinternals tool for that, but personally >> >> i >> >> would use powershell and do a get-process >> >> >> >> >> >> "Frank" <Frank@discussions.microsoft.com> wrote in message >> >> news:55CB144B-452D-4F5C-AB33-3B1C650FEB68@microsoft.com... >> >> > Hi Justin, >> >> > >> >> > This numbers are the same after a reboot. SQL server is configured >> >> > to >> >> > use >> >> > a >> >> > fixed amount of memory between 1.5 and 2.5 Gb and in the past this >> >> > would >> >> > result in the use of at least 1.7 Gb of physical memory, now it uses >> >> > 1.7 >> >> > Gb >> >> > of virtual memory as there is almost no physical memory available. >> >> > >> >> > best regards, >> >> > >> >> > Frank >> > >> >> >>
Guest Frank Posted June 12, 2008 Posted June 12, 2008 Re: Memory issue Hi Justin, Physical memory: 4193268 Available: 237660 System cache: 382088 Kernel memory Total: 156096 Paged: 116344 Nonpaged: 39752 As you can see I am missing around 3 GB of memory.... :-( On a "good" server Physical memory: 4191916 Available: 1757600 System cache: 801940 Kernel memory Total: 175864 Paged: 125344 Nonpaged: 50520 Thnx for your help sofar. Frank "Justin Rich" wrote: > yeah your working set is a bit on the tiny side... > what does task manager say your system cache is taking? and total kernel > memory? > > "Frank" <Frank@discussions.microsoft.com> wrote in message > news:C9C4C7CA-58AD-4A9E-897C-6FCAA837008E@microsoft.com... > > Hi Justin, > > > > Sorry for the mix up KB - MB. I meant MB. > > > > To start with the result of pslist -m > > > > Name Pid VM WS Priv Priv Pk Faults NonP > > Page > > Idle 0 0 28 0 0 0 0 > > 0 > > System 4 1940 228 0 0 10759027 0 > > 0 > > smss 288 3548 248 132 172 359 0 > > 6 > > csrss 336 29200 2528 1892 3612 18004 5 > > 75 > > winlogon 364 62908 5480 10876 13668 145423 51 > > 101 > > services 412 49956 3840 1976 2060 70414 8 > > 92 > > lsass 424 42444 4008 7544 7824 15870 14 > > 56 > > svchost 640 19680 1096 888 944 2992 2 > > 35 > > svchost 704 22204 2508 1584 1632 7102 20 > > 40 > > svchost 768 41256 1580 3932 4000 7657 5 > > 64 > > svchost 804 26072 2184 4280 4328 6261 6 > > 39 > > svchost 820 169360 23508 24120 35276 365800 53 > > 170 > > spoolsv 952 29924 3552 3940 4524 53473 4 > > 44 > > msdtc 976 25448 520 1940 1988 1581 16 > > 40 > > BackupClientService 1104 82164 7268 10380 21296 59046490 5 > > 76 > > svchost 1180 17204 200 576 600 603 2 > > 33 > > sqlservr 1252 1787020 33992 77384 78664 430705 173 > > 107 > > svchost 1328 7232 200 304 332 388 1 > > 15 > > snmp 1376 42760 1588 3928 4492 11500 7 > > 65 > > SQBCoreService 1424 66812 1116 6976 33140 412501 5 > > 67 > > mqsvc 1912 38220 288 3404 3620 2019 129 > > 63 > > mssearch 1968 34060 440 5632 5656 3246 4 > > 56 > > sqlagent 1528 43896 1704 2624 2932 14570 4 > > 63 > > svchost 1656 33340 1208 2924 2972 1932 6 > > 55 > > svchost 1420 59652 2004 2600 23148 7049 5 > > 59 > > csrss 3060 22944 200 852 896 861 3 > > 43 > > winlogon 3084 33508 376 1608 2612 2586 4 > > 60 > > rdpclip 3216 33084 1608 1084 1100 3308 2 > > 62 > > explorer 3316 74268 10136 8396 10608 9787780 10 > > 125 > > BacsTray 3552 32400 608 896 908 2034 2 > > 57 > > BackupClient 3580 36216 1300 1636 1760 9540 2 > > 59 > > ctfmon 3612 26072 1876 596 896 10074 3 > > 52 > > sqlmangr 3620 37516 1136 1412 2800 2611 3 > > 66 > > wmiprvse 2524 27416 568 1844 2424 7816 3 > > 45 > > logon.scr 304 14144 220 344 344 653 1 > > 29 > > inetinfo 1004 48360 2012 3176 3376 8605 5 > > 69 > > NTRtScan 3464 148664 15184 13536 14444 1465266 12 > > 78 > > TmListen 1792 117584 9240 10872 14444 442991 43 > > 102 > > PccNTMon 676 45380 4184 3204 4500 73452 5 > > 71 > > TmPfw 1688 43840 1752 1408 2652 22065 5 > > 65 > > CNTAoSMgr 3780 21860 552 1132 1144 1057 2 > > 31 > > TmProxy 2728 30676 272 1692 4324 6801 34 > > 37 > > cmd 4732 13996 704 1476 1532 646 1 > > 27 > > wuauclt 4720 33960 3860 2012 2044 1119 3 > > 63 > > wmiprvse 632 29332 5356 2240 2712 1452 3 > > 47 > > pslist 5928 27520 2684 1000 1016 811 2 > > 47 > > > > According to MS AWE should not be enabled on servers with 4 GB or less. > > However I have tried it and it did not solve the problem. > > > >> based on what i've seen so far this looks pretty normal. > > > > We have about 15 other DB servers and believe me this is not normal. Below > > is a listing of another DB server. Both servers have 4 Gb memory, and both > > have the /PAE and the /3Gb enabled. > > > > Name Pid VM WS Priv Priv Pk Faults NonP > > Page > > Idle 0 0 28 0 0 0 0 > > 0 > > System 4 1940 240 0 0 12730350 0 > > 0 > > smss 328 3548 480 128 168 371 0 > > 6 > > csrss 376 29212 4748 1880 1988 8220 6 > > 83 > > winlogon 404 60612 8284 9672 12332 100872 43 > > 97 > > services 452 61212 24436 4304 12256 54017 13 > > 107 > > lsass 464 50288 9196 8596 8664 6642 20 > > 64 > > svchost 696 19420 2788 864 944 871 2 > > 35 > > svchost 748 22116 3572 1376 1464 1157 20 > > 39 > > svchost 812 43088 4660 3912 4028 3641 6 > > 64 > > svchost 848 25772 5776 3752 3800 2081 6 > > 39 > > svchost 864 149772 33392 25972 45392 2100416 55 > > 167 > > spoolsv 996 29648 5912 4012 4520 12835 4 > > 43 > > msdtc 1020 24540 4476 1868 1916 1214 5 > > 38 > > BackupClientService 1156 73456 11544 7860 16192 59648100 5 > > 76 > > cimntfy 1172 32236 3632 1116 1132 923 3 > > 54 > > cissesrv 1196 7084 1424 260 284 53300 1 > > 15 > > cpqrcmc 1208 7336 1324 280 284 329 1 > > 15 > > vcagent 1224 32088 6996 2328 2496 1887 2 > > 53 > > svchost 1256 17204 2224 576 600 600 2 > > 33 > > inetinfo 1336 49312 8944 3376 5408 12618 5 > > 69 > > sqlservr 1424 1833320 1783240 1745952 1746948 1321535 19 > > 126 > > svchost 1568 13844 2624 936 936 1197 2 > > 23 > > snmp 1596 56960 4372 10720 12880 27825 9 > > 81 > > SQBCoreService 1656 67832 9708 6964 34428 316306 5 > > 67 > > sysdown 1768 10608 1480 336 336 366 1 > > 21 > > smhstart 1784 17408 3248 1344 1344 811 2 > > 28 > > hpsmhd 1920 39504 11116 7468 7944 33429 246 > > 66 > > cpqnimgt 2044 50688 6396 3484 4064 1629 4 > > 70 > > cqmgserv 2100 36256 4976 3576 3576 866074 5 > > 55 > > cqmgstor 2120 27864 4524 3704 3772 1164 7 > > 47 > > mssearch 2144 34056 1300 4136 4168 1976 4 > > 56 > > wmiprvse 2284 30548 6588 3100 4908 2950 3 > > 45 > > svchost 2332 32480 7760 5020 6984 7952 5 > > 39 > > rotatelogs 2500 20872 1940 620 620 494 1 > > 40 > > rotatelogs 2508 20872 1916 612 612 488 1 > > 40 > > hpsmhd 2552 105552 17224 14956 14968 37236 29 > > 74 > > cqmghost 2680 42852 7052 3420 3640 9972022 6 > > 66 > > rotatelogs 2720 20872 1948 620 620 496 1 > > 40 > > rotatelogs 2728 20872 1924 612 612 490 1 > > 40 > > sqlagent 2880 45432 3304 2684 2972 5495 5 > > 63 > > svchost 4004 33596 4028 2956 3028 1082 6 > > 55 > > svchost 1520 58372 4808 2596 23100 8265 5 > > 59 > > wmiprvse 4316 46964 8488 4888 5368 308082 5 > > 69 > > explorer 4936 74976 15992 7972 9648 9136526 11 > > 128 > > cpqteam 5004 26064 2636 612 612 793 1 > > 49 > > jusched 5016 38044 5836 1564 1584 1654 5 > > 70 > > BackupClient 5032 37256 3020 1716 1820 4704 2 > > 61 > > ctfmon 5052 17544 4608 528 896 1602 3 > > 34 > > sqlmangr 5060 38556 5340 1464 2852 2393 3 > > 67 > > csrss 4044 22940 2612 896 944 974 3 > > 43 > > winlogon 4720 33508 5008 1660 1732 1688 4 > > 60 > > rdpclip 5664 32828 3992 1040 1072 1322 2 > > 61 > > logon.scr 5080 14144 1656 344 344 447 1 > > 29 > > NTRtScan 4708 95236 16820 11680 12652 1264245 9 > > 68 > > TmListen 4900 117660 17472 10264 12700 229087 43 > > 102 > > PccNTMon 1028 47428 7880 3208 4504 35788 5 > > 71 > > TmPfw 4884 43836 5420 1408 2636 11105 5 > > 65 > > CNTAoSMgr 5676 21856 2652 1132 1144 685 2 > > 31 > > TmProxy 5884 30676 5132 1452 2764 2914 34 > > 37 > > w3wp 584 40276 6892 3604 3632 2835 7 > > 45 > > wuauclt 2056 34468 3976 2044 2044 1137 3 > > 63 > > > > IF you compare the SQLServer prcess you can see that on the "good" server > > the physical memory used is around 1.7 GB however on the "bad" server it > > is > > only 33 MB > > > > sqlservr 1424 1833320 1783240 1745952 1746948 1321535 19 > > 126 > > sqlservr 1252 1787020 33992 77384 78664 430705 > > 173 107 > > > > My guess is that SQL is not the problem here. If I shut down SQL server I > > only get around 33 MB back. Something is eating my physical memory and it > > is > > not showing up in any program or taskmanager. > > > > It could be a bug in Windows or there is a serious problem with my server > > hardware. > > > > > > best regards, > > > > Frank > > > > "Justin Rich" wrote: > > > >> What you have listed is the Private Virtual memory (Priv) and Virtual > >> Memory. you are seeing roughly 270MB (not KB) of priv and about 3.5GB of > >> Virtual Memory. > >> The working set (ws) values would be of use. Although the working set is > >> not > >> an exact representation of what is in physical ram, its pretty close. > >> Also its important to keep in mind that "Virtual Memory" does not mean > >> its > >> not in physical ram. VM is the virtual address space that the application > >> is > >> aware of. > >> > >> Also i see that SQL is using 1.7GB which is about right for a standard 32 > >> bit system. the odd part is you are using the /3GB switch so it should be > >> a > >> bit more. > >> run this and let me see the results > >> pslist -m > >> > >> based on what i've seen so far this looks pretty normal. the one thing > >> you > >> might want to take a look at is the SQL end of things. your 1.7GB of sql > >> VM > >> looks as though SQL is not configured correctly. 1.7 is the typical max > >> you > >> would see for a standard 32bit system without /3GB (1.7 being as close as > >> i've seen sql get to the 2gb limit) > >> > >> you may want to get rid of the /3gb and just use the /pae and then > >> configure > >> sql to use awe > >> http://support.microsoft.com/kb/274750 (might be a new article, but this
Guest Justin Rich Posted June 12, 2008 Posted June 12, 2008 Re: Memory issue no idea what to tell you... maybe look for an app that does memory analysis or perhaps try memdefrag... but.. thats just weird "Frank" <Frank@discussions.microsoft.com> wrote in message news:20E5583A-9133-42CB-9ACC-3FE083CB1319@microsoft.com... > Hi Justin, > > Physical memory: 4193268 > Available: 237660 > System cache: 382088 > > Kernel memory > Total: 156096 > Paged: 116344 > Nonpaged: 39752 > > As you can see I am missing around 3 GB of memory.... :-( > > On a "good" server > Physical memory: 4191916 > Available: 1757600 > System cache: 801940 > > Kernel memory > Total: 175864 > Paged: 125344 > Nonpaged: 50520 > > Thnx for your help sofar. > > Frank > > "Justin Rich" wrote: > >> yeah your working set is a bit on the tiny side... >> what does task manager say your system cache is taking? and total kernel >> memory? >> >> "Frank" <Frank@discussions.microsoft.com> wrote in message >> news:C9C4C7CA-58AD-4A9E-897C-6FCAA837008E@microsoft.com... >> > Hi Justin, >> > >> > Sorry for the mix up KB - MB. I meant MB. >> > >> > To start with the result of pslist -m >> > >> > Name Pid VM WS Priv Priv Pk Faults NonP >> > Page >> > Idle 0 0 28 0 0 0 0 >> > 0 >> > System 4 1940 228 0 0 10759027 0 >> > 0 >> > smss 288 3548 248 132 172 359 0 >> > 6 >> > csrss 336 29200 2528 1892 3612 18004 5 >> > 75 >> > winlogon 364 62908 5480 10876 13668 145423 51 >> > 101 >> > services 412 49956 3840 1976 2060 70414 8 >> > 92 >> > lsass 424 42444 4008 7544 7824 15870 14 >> > 56 >> > svchost 640 19680 1096 888 944 2992 2 >> > 35 >> > svchost 704 22204 2508 1584 1632 7102 20 >> > 40 >> > svchost 768 41256 1580 3932 4000 7657 5 >> > 64 >> > svchost 804 26072 2184 4280 4328 6261 6 >> > 39 >> > svchost 820 169360 23508 24120 35276 365800 53 >> > 170 >> > spoolsv 952 29924 3552 3940 4524 53473 4 >> > 44 >> > msdtc 976 25448 520 1940 1988 1581 16 >> > 40 >> > BackupClientService 1104 82164 7268 10380 21296 59046490 >> > 5 >> > 76 >> > svchost 1180 17204 200 576 600 603 2 >> > 33 >> > sqlservr 1252 1787020 33992 77384 78664 430705 173 >> > 107 >> > svchost 1328 7232 200 304 332 388 1 >> > 15 >> > snmp 1376 42760 1588 3928 4492 11500 7 >> > 65 >> > SQBCoreService 1424 66812 1116 6976 33140 412501 5 >> > 67 >> > mqsvc 1912 38220 288 3404 3620 2019 129 >> > 63 >> > mssearch 1968 34060 440 5632 5656 3246 4 >> > 56 >> > sqlagent 1528 43896 1704 2624 2932 14570 4 >> > 63 >> > svchost 1656 33340 1208 2924 2972 1932 6 >> > 55 >> > svchost 1420 59652 2004 2600 23148 7049 5 >> > 59 >> > csrss 3060 22944 200 852 896 861 3 >> > 43 >> > winlogon 3084 33508 376 1608 2612 2586 4 >> > 60 >> > rdpclip 3216 33084 1608 1084 1100 3308 2 >> > 62 >> > explorer 3316 74268 10136 8396 10608 9787780 10 >> > 125 >> > BacsTray 3552 32400 608 896 908 2034 2 >> > 57 >> > BackupClient 3580 36216 1300 1636 1760 9540 2 >> > 59 >> > ctfmon 3612 26072 1876 596 896 10074 3 >> > 52 >> > sqlmangr 3620 37516 1136 1412 2800 2611 3 >> > 66 >> > wmiprvse 2524 27416 568 1844 2424 7816 3 >> > 45 >> > logon.scr 304 14144 220 344 344 653 1 >> > 29 >> > inetinfo 1004 48360 2012 3176 3376 8605 5 >> > 69 >> > NTRtScan 3464 148664 15184 13536 14444 1465266 12 >> > 78 >> > TmListen 1792 117584 9240 10872 14444 442991 43 >> > 102 >> > PccNTMon 676 45380 4184 3204 4500 73452 5 >> > 71 >> > TmPfw 1688 43840 1752 1408 2652 22065 5 >> > 65 >> > CNTAoSMgr 3780 21860 552 1132 1144 1057 2 >> > 31 >> > TmProxy 2728 30676 272 1692 4324 6801 34 >> > 37 >> > cmd 4732 13996 704 1476 1532 646 1 >> > 27 >> > wuauclt 4720 33960 3860 2012 2044 1119 3 >> > 63 >> > wmiprvse 632 29332 5356 2240 2712 1452 3 >> > 47 >> > pslist 5928 27520 2684 1000 1016 811 2 >> > 47 >> > >> > According to MS AWE should not be enabled on servers with 4 GB or less. >> > However I have tried it and it did not solve the problem. >> > >> >> based on what i've seen so far this looks pretty normal. >> > >> > We have about 15 other DB servers and believe me this is not normal. >> > Below >> > is a listing of another DB server. Both servers have 4 Gb memory, and >> > both >> > have the /PAE and the /3Gb enabled. >> > >> > Name Pid VM WS Priv Priv Pk Faults NonP >> > Page >> > Idle 0 0 28 0 0 0 0 >> > 0 >> > System 4 1940 240 0 0 12730350 0 >> > 0 >> > smss 328 3548 480 128 168 371 0 >> > 6 >> > csrss 376 29212 4748 1880 1988 8220 6 >> > 83 >> > winlogon 404 60612 8284 9672 12332 100872 43 >> > 97 >> > services 452 61212 24436 4304 12256 54017 13 >> > 107 >> > lsass 464 50288 9196 8596 8664 6642 20 >> > 64 >> > svchost 696 19420 2788 864 944 871 2 >> > 35 >> > svchost 748 22116 3572 1376 1464 1157 20 >> > 39 >> > svchost 812 43088 4660 3912 4028 3641 6 >> > 64 >> > svchost 848 25772 5776 3752 3800 2081 6 >> > 39 >> > svchost 864 149772 33392 25972 45392 2100416 55 >> > 167 >> > spoolsv 996 29648 5912 4012 4520 12835 4 >> > 43 >> > msdtc 1020 24540 4476 1868 1916 1214 5 >> > 38 >> > BackupClientService 1156 73456 11544 7860 16192 59648100 >> > 5 >> > 76 >> > cimntfy 1172 32236 3632 1116 1132 923 3 >> > 54 >> > cissesrv 1196 7084 1424 260 284 53300 1 >> > 15 >> > cpqrcmc 1208 7336 1324 280 284 329 1 >> > 15 >> > vcagent 1224 32088 6996 2328 2496 1887 2 >> > 53 >> > svchost 1256 17204 2224 576 600 600 2 >> > 33 >> > inetinfo 1336 49312 8944 3376 5408 12618 5 >> > 69 >> > sqlservr 1424 1833320 1783240 1745952 1746948 1321535 19 >> > 126 >> > svchost 1568 13844 2624 936 936 1197 2 >> > 23 >> > snmp 1596 56960 4372 10720 12880 27825 9 >> > 81 >> > SQBCoreService 1656 67832 9708 6964 34428 316306 5 >> > 67 >> > sysdown 1768 10608 1480 336 336 366 1 >> > 21 >> > smhstart 1784 17408 3248 1344 1344 811 2 >> > 28 >> > hpsmhd 1920 39504 11116 7468 7944 33429 246 >> > 66 >> > cpqnimgt 2044 50688 6396 3484 4064 1629 4 >> > 70 >> > cqmgserv 2100 36256 4976 3576 3576 866074 5 >> > 55 >> > cqmgstor 2120 27864 4524 3704 3772 1164 7 >> > 47 >> > mssearch 2144 34056 1300 4136 4168 1976 4 >> > 56 >> > wmiprvse 2284 30548 6588 3100 4908 2950 3 >> > 45 >> > svchost 2332 32480 7760 5020 6984 7952 5 >> > 39 >> > rotatelogs 2500 20872 1940 620 620 494 1 >> > 40 >> > rotatelogs 2508 20872 1916 612 612 488 1 >> > 40 >> > hpsmhd 2552 105552 17224 14956 14968 37236 29 >> > 74 >> > cqmghost 2680 42852 7052 3420 3640 9972022 6 >> > 66 >> > rotatelogs 2720 20872 1948 620 620 496 1 >> > 40 >> > rotatelogs 2728 20872 1924 612 612 490 1 >> > 40 >> > sqlagent 2880 45432 3304 2684 2972 5495 5 >> > 63 >> > svchost 4004 33596 4028 2956 3028 1082 6 >> > 55 >> > svchost 1520 58372 4808 2596 23100 8265 5 >> > 59 >> > wmiprvse 4316 46964 8488 4888 5368 308082 5 >> > 69 >> > explorer 4936 74976 15992 7972 9648 9136526 11 >> > 128 >> > cpqteam 5004 26064 2636 612 612 793 1 >> > 49 >> > jusched 5016 38044 5836 1564 1584 1654 5 >> > 70 >> > BackupClient 5032 37256 3020 1716 1820 4704 2 >> > 61 >> > ctfmon 5052 17544 4608 528 896 1602 3 >> > 34 >> > sqlmangr 5060 38556 5340 1464 2852 2393 3 >> > 67 >> > csrss 4044 22940 2612 896 944 974 3 >> > 43 >> > winlogon 4720 33508 5008 1660 1732 1688 4 >> > 60 >> > rdpclip 5664 32828 3992 1040 1072 1322 2 >> > 61 >> > logon.scr 5080 14144 1656 344 344 447 1 >> > 29 >> > NTRtScan 4708 95236 16820 11680 12652 1264245 9 >> > 68 >> > TmListen 4900 117660 17472 10264 12700 229087 43 >> > 102 >> > PccNTMon 1028 47428 7880 3208 4504 35788 5 >> > 71 >> > TmPfw 4884 43836 5420 1408 2636 11105 5 >> > 65 >> > CNTAoSMgr 5676 21856 2652 1132 1144 685 2 >> > 31 >> > TmProxy 5884 30676 5132 1452 2764 2914 34 >> > 37 >> > w3wp 584 40276 6892 3604 3632 2835 7 >> > 45 >> > wuauclt 2056 34468 3976 2044 2044 1137 3 >> > 63 >> > >> > IF you compare the SQLServer prcess you can see that on the "good" >> > server >> > the physical memory used is around 1.7 GB however on the "bad" server >> > it >> > is >> > only 33 MB >> > >> > sqlservr 1424 1833320 1783240 1745952 1746948 1321535 19 >> > 126 >> > sqlservr 1252 1787020 33992 77384 78664 430705 >> > 173 107 >> > >> > My guess is that SQL is not the problem here. If I shut down SQL server >> > I >> > only get around 33 MB back. Something is eating my physical memory and >> > it >> > is >> > not showing up in any program or taskmanager. >> > >> > It could be a bug in Windows or there is a serious problem with my >> > server >> > hardware. >> > >> > >> > best regards, >> > >> > Frank >> > >> > "Justin Rich" wrote: >> > >> >> What you have listed is the Private Virtual memory (Priv) and Virtual >> >> Memory. you are seeing roughly 270MB (not KB) of priv and about 3.5GB >> >> of >> >> Virtual Memory. >> >> The working set (ws) values would be of use. Although the working set >> >> is >> >> not >> >> an exact representation of what is in physical ram, its pretty close. >> >> Also its important to keep in mind that "Virtual Memory" does not mean >> >> its >> >> not in physical ram. VM is the virtual address space that the >> >> application >> >> is >> >> aware of. >> >> >> >> Also i see that SQL is using 1.7GB which is about right for a standard >> >> 32 >> >> bit system. the odd part is you are using the /3GB switch so it should >> >> be >> >> a >> >> bit more. >> >> run this and let me see the results >> >> pslist -m >> >> >> >> based on what i've seen so far this looks pretty normal. the one thing >> >> you >> >> might want to take a look at is the SQL end of things. your 1.7GB of >> >> sql >> >> VM >> >> looks as though SQL is not configured correctly. 1.7 is the typical >> >> max >> >> you >> >> would see for a standard 32bit system without /3GB (1.7 being as close >> >> as >> >> i've seen sql get to the 2gb limit) >> >> >> >> you may want to get rid of the /3gb and just use the /pae and then >> >> configure >> >> sql to use awe >> >> http://support.microsoft.com/kb/274750 (might be a new article, but >> >> this
Guest Frank Posted June 16, 2008 Posted June 16, 2008 Re: Memory issue Fixed the problem. Seems that for some reason in the boot.ini all switches were being ignored. Deleted the file, copied the file form a working server (that had exactly the same content!) and rebooted the server. Now I have 4 Gb available again. "Justin Rich" wrote: > no idea what to tell you... maybe look for an app that does memory analysis > or perhaps try memdefrag... but.. thats just weird > > > "Frank" <Frank@discussions.microsoft.com> wrote in message > news:20E5583A-9133-42CB-9ACC-3FE083CB1319@microsoft.com... > > Hi Justin, > > > > Physical memory: 4193268 > > Available: 237660 > > System cache: 382088 > > > > Kernel memory > > Total: 156096 > > Paged: 116344 > > Nonpaged: 39752 > > > > As you can see I am missing around 3 GB of memory.... :-( > > > > On a "good" server > > Physical memory: 4191916 > > Available: 1757600 > > System cache: 801940 > > > > Kernel memory > > Total: 175864 > > Paged: 125344 > > Nonpaged: 50520 > > > > Thnx for your help sofar. > > > > Frank > > > > "Justin Rich" wrote: > > > >> yeah your working set is a bit on the tiny side... > >> what does task manager say your system cache is taking? and total kernel > >> memory? > >> > >> "Frank" <Frank@discussions.microsoft.com> wrote in message > >> news:C9C4C7CA-58AD-4A9E-897C-6FCAA837008E@microsoft.com... > >> > Hi Justin, > >> > > >> > Sorry for the mix up KB - MB. I meant MB. > >> > > >> > To start with the result of pslist -m > >> > > >> > Name Pid VM WS Priv Priv Pk Faults NonP > >> > Page > >> > Idle 0 0 28 0 0 0 0 > >> > 0 > >> > System 4 1940 228 0 0 10759027 0 > >> > 0 > >> > smss 288 3548 248 132 172 359 0 > >> > 6 > >> > csrss 336 29200 2528 1892 3612 18004 5 > >> > 75 > >> > winlogon 364 62908 5480 10876 13668 145423 51 > >> > 101 > >> > services 412 49956 3840 1976 2060 70414 8 > >> > 92 > >> > lsass 424 42444 4008 7544 7824 15870 14 > >> > 56 > >> > svchost 640 19680 1096 888 944 2992 2 > >> > 35 > >> > svchost 704 22204 2508 1584 1632 7102 20 > >> > 40 > >> > svchost 768 41256 1580 3932 4000 7657 5 > >> > 64 > >> > svchost 804 26072 2184 4280 4328 6261 6 > >> > 39 > >> > svchost 820 169360 23508 24120 35276 365800 53 > >> > 170 > >> > spoolsv 952 29924 3552 3940 4524 53473 4 > >> > 44 > >> > msdtc 976 25448 520 1940 1988 1581 16 > >> > 40 > >> > BackupClientService 1104 82164 7268 10380 21296 59046490 > >> > 5 > >> > 76 > >> > svchost 1180 17204 200 576 600 603 2 > >> > 33 > >> > sqlservr 1252 1787020 33992 77384 78664 430705 173 > >> > 107 > >> > svchost 1328 7232 200 304 332 388 1 > >> > 15 > >> > snmp 1376 42760 1588 3928 4492 11500 7 > >> > 65 > >> > SQBCoreService 1424 66812 1116 6976 33140 412501 5 > >> > 67 > >> > mqsvc 1912 38220 288 3404 3620 2019 129 > >> > 63 > >> > mssearch 1968 34060 440 5632 5656 3246 4 > >> > 56 > >> > sqlagent 1528 43896 1704 2624 2932 14570 4 > >> > 63 > >> > svchost 1656 33340 1208 2924 2972 1932 6 > >> > 55 > >> > svchost 1420 59652 2004 2600 23148 7049 5 > >> > 59 > >> > csrss 3060 22944 200 852 896 861 3 > >> > 43 > >> > winlogon 3084 33508 376 1608 2612 2586 4 > >> > 60 > >> > rdpclip 3216 33084 1608 1084 1100 3308 2 > >> > 62 > >> > explorer 3316 74268 10136 8396 10608 9787780 10 > >> > 125 > >> > BacsTray 3552 32400 608 896 908 2034 2 > >> > 57 > >> > BackupClient 3580 36216 1300 1636 1760 9540 2 > >> > 59 > >> > ctfmon 3612 26072 1876 596 896 10074 3 > >> > 52 > >> > sqlmangr 3620 37516 1136 1412 2800 2611 3 > >> > 66 > >> > wmiprvse 2524 27416 568 1844 2424 7816 3 > >> > 45 > >> > logon.scr 304 14144 220 344 344 653 1 > >> > 29 > >> > inetinfo 1004 48360 2012 3176 3376 8605 5 > >> > 69 > >> > NTRtScan 3464 148664 15184 13536 14444 1465266 12 > >> > 78 > >> > TmListen 1792 117584 9240 10872 14444 442991 43 > >> > 102 > >> > PccNTMon 676 45380 4184 3204 4500 73452 5 > >> > 71 > >> > TmPfw 1688 43840 1752 1408 2652 22065 5 > >> > 65 > >> > CNTAoSMgr 3780 21860 552 1132 1144 1057 2 > >> > 31 > >> > TmProxy 2728 30676 272 1692 4324 6801 34 > >> > 37 > >> > cmd 4732 13996 704 1476 1532 646 1 > >> > 27 > >> > wuauclt 4720 33960 3860 2012 2044 1119 3 > >> > 63 > >> > wmiprvse 632 29332 5356 2240 2712 1452 3 > >> > 47 > >> > pslist 5928 27520 2684 1000 1016 811 2 > >> > 47 > >> > > >> > According to MS AWE should not be enabled on servers with 4 GB or less. > >> > However I have tried it and it did not solve the problem. > >> > > >> >> based on what i've seen so far this looks pretty normal. > >> > > >> > We have about 15 other DB servers and believe me this is not normal. > >> > Below > >> > is a listing of another DB server. Both servers have 4 Gb memory, and > >> > both > >> > have the /PAE and the /3Gb enabled. > >> > > >> > Name Pid VM WS Priv Priv Pk Faults NonP > >> > Page > >> > Idle 0 0 28 0 0 0 0 > >> > 0 > >> > System 4 1940 240 0 0 12730350 0 > >> > 0 > >> > smss 328 3548 480 128 168 371 0 > >> > 6 > >> > csrss 376 29212 4748 1880 1988 8220 6 > >> > 83 > >> > winlogon 404 60612 8284 9672 12332 100872 43 > >> > 97 > >> > services 452 61212 24436 4304 12256 54017 13 > >> > 107 > >> > lsass 464 50288 9196 8596 8664 6642 20 > >> > 64 > >> > svchost 696 19420 2788 864 944 871 2 > >> > 35 > >> > svchost 748 22116 3572 1376 1464 1157 20 > >> > 39 > >> > svchost 812 43088 4660 3912 4028 3641 6 > >> > 64 > >> > svchost 848 25772 5776 3752 3800 2081 6 > >> > 39 > >> > svchost 864 149772 33392 25972 45392 2100416 55 > >> > 167 > >> > spoolsv 996 29648 5912 4012 4520 12835 4 > >> > 43 > >> > msdtc 1020 24540 4476 1868 1916 1214 5 > >> > 38 > >> > BackupClientService 1156 73456 11544 7860 16192 59648100 > >> > 5 > >> > 76 > >> > cimntfy 1172 32236 3632 1116 1132 923 3 > >> > 54 > >> > cissesrv 1196 7084 1424 260 284 53300 1 > >> > 15 > >> > cpqrcmc 1208 7336 1324 280 284 329 1 > >> > 15 > >> > vcagent 1224 32088 6996 2328 2496 1887 2 > >> > 53 > >> > svchost 1256 17204 2224 576 600 600 2 > >> > 33 > >> > inetinfo 1336 49312 8944 3376 5408 12618 5 > >> > 69 > >> > sqlservr 1424 1833320 1783240 1745952 1746948 1321535 19 > >> > 126 > >> > svchost 1568 13844 2624 936 936 1197 2 > >> > 23 > >> > snmp 1596 56960 4372 10720 12880 27825 9 > >> > 81 > >> > SQBCoreService 1656 67832 9708 6964 34428 316306 5 > >> > 67 > >> > sysdown 1768 10608 1480 336 336 366 1 > >> > 21 > >> > smhstart 1784 17408 3248 1344 1344 811 2 > >> > 28 > >> > hpsmhd 1920 39504 11116 7468 7944 33429 246 > >> > 66 > >> > cpqnimgt 2044 50688 6396 3484 4064 1629 4 > >> > 70 > >> > cqmgserv 2100 36256 4976 3576 3576 866074 5 > >> > 55 > >> > cqmgstor 2120 27864 4524 3704 3772 1164 7 > >> > 47 > >> > mssearch 2144 34056 1300 4136 4168 1976 4 > >> > 56 > >> > wmiprvse 2284 30548 6588 3100 4908 2950 3 > >> > 45 > >> > svchost 2332 32480 7760 5020 6984 7952 5 > >> > 39 > >> > rotatelogs 2500 20872 1940 620 620 494 1 > >> > 40 > >> > rotatelogs 2508 20872 1916 612 612 488 1 > >> > 40 > >> > hpsmhd 2552 105552 17224 14956 14968 37236 29 > >> > 74 > >> > cqmghost 2680 42852 7052 3420 3640 9972022 6 > >> > 66 > >> > rotatelogs 2720 20872 1948 620 620 496 1 > >> > 40 > >> > rotatelogs 2728 20872 1924 612 612 490 1 > >> > 40 > >> > sqlagent 2880 45432 3304 2684 2972 5495 5 > >> > 63 > >> > svchost 4004 33596 4028 2956 3028 1082 6 > >> > 55 > >> > svchost 1520 58372 4808 2596 23100 8265 5 > >> > 59 > >> > wmiprvse 4316 46964 8488 4888 5368 308082 5 > >> > 69 > >> > explorer 4936 74976 15992 7972 9648 9136526 11 > >> > 128 > >> > cpqteam 5004 26064 2636 612 612 793 1 > >> > 49 > >> > jusched 5016 38044 5836 1564 1584 1654 5 > >> > 70 > >> > BackupClient 5032 37256 3020 1716 1820 4704 2 > >> > 61 > >> > ctfmon 5052 17544 4608 528 896 1602 3 > >> > 34 > >> > sqlmangr 5060 38556 5340 1464 2852 2393 3 > >> > 67 > >> > csrss 4044 22940 2612 896 944 974 3 > >> > 43 > >> > winlogon 4720 33508 5008 1660 1732 1688 4 > >> > 60 > >> > rdpclip 5664 32828 3992 1040 1072 1322 2 > >> > 61 > >> > logon.scr 5080 14144 1656 344 344 447 1 > >> > 29 > >> > NTRtScan 4708 95236 16820 11680 12652 1264245 9 > >> > 68 > >> > TmListen 4900 117660 17472 10264 12700 229087 43 > >> > 102 > >> > PccNTMon 1028 47428 7880 3208 4504 35788 5 > >> > 71 > >> > TmPfw 4884 43836 5420 1408 2636 11105 5 > >> > 65 > >> > CNTAoSMgr 5676 21856 2652 1132 1144 685 2 > >> > 31 > >> > TmProxy 5884 30676 5132 1452 2764 2914 34 > >> > 37 > >> > w3wp 584 40276 6892 3604 3632 2835 7 > >> > 45 > >> > wuauclt 2056 34468 3976 2044 2044 1137 3 > >> > 63 > >> > > >> > IF you compare the SQLServer prcess you can see that on the "good" > >> > server > >> > the physical memory used is around 1.7 GB however on the "bad" server > >> > it > >> > is > >> > only 33 MB > >> > > >> > sqlservr 1424 1833320 1783240 1745952 1746948 1321535 19 > >> > 126 > >> > sqlservr 1252 1787020 33992 77384 78664 430705 > >> > 173 107 > >> > > >> > My guess is that SQL is not the problem here. If I shut down SQL server > >> > I > >> > only get around 33 MB back. Something is eating my physical memory and > >> > it > >> > is > >> > not showing up in any program or taskmanager.
Guest Justin Rich Posted June 16, 2008 Posted June 16, 2008 Re: Memory issue weird solution.. even if you had no switches it shouldnt have done what it was doing... anyways, glad you got it fixed... "Frank" <Frank@discussions.microsoft.com> wrote in message news:68EC3D3C-3628-40F1-8E7D-59FAE80CD19C@microsoft.com... > Fixed the problem. Seems that for some reason in the boot.ini all switches > were being ignored. Deleted the file, copied the file form a working > server > (that had exactly the same content!) and rebooted the server. > > Now I have 4 Gb available again. > > > > "Justin Rich" wrote: > >> no idea what to tell you... maybe look for an app that does memory >> analysis >> or perhaps try memdefrag... but.. thats just weird >> >> >> "Frank" <Frank@discussions.microsoft.com> wrote in message >> news:20E5583A-9133-42CB-9ACC-3FE083CB1319@microsoft.com... >> > Hi Justin, >> > >> > Physical memory: 4193268 >> > Available: 237660 >> > System cache: 382088 >> > >> > Kernel memory >> > Total: 156096 >> > Paged: 116344 >> > Nonpaged: 39752 >> > >> > As you can see I am missing around 3 GB of memory.... :-( >> > >> > On a "good" server >> > Physical memory: 4191916 >> > Available: 1757600 >> > System cache: 801940 >> > >> > Kernel memory >> > Total: 175864 >> > Paged: 125344 >> > Nonpaged: 50520 >> > >> > Thnx for your help sofar. >> > >> > Frank >> > >> > "Justin Rich" wrote: >> > >> >> yeah your working set is a bit on the tiny side... >> >> what does task manager say your system cache is taking? and total >> >> kernel >> >> memory? >> >> >> >> "Frank" <Frank@discussions.microsoft.com> wrote in message >> >> news:C9C4C7CA-58AD-4A9E-897C-6FCAA837008E@microsoft.com... >> >> > Hi Justin, >> >> > >> >> > Sorry for the mix up KB - MB. I meant MB. >> >> > >> >> > To start with the result of pslist -m >> >> > >> >> > Name Pid VM WS Priv Priv Pk Faults >> >> > NonP >> >> > Page >> >> > Idle 0 0 28 0 0 0 >> >> > 0 >> >> > 0 >> >> > System 4 1940 228 0 0 10759027 >> >> > 0 >> >> > 0 >> >> > smss 288 3548 248 132 172 359 >> >> > 0 >> >> > 6 >> >> > csrss 336 29200 2528 1892 3612 18004 >> >> > 5 >> >> > 75 >> >> > winlogon 364 62908 5480 10876 13668 145423 >> >> > 51 >> >> > 101 >> >> > services 412 49956 3840 1976 2060 70414 >> >> > 8 >> >> > 92 >> >> > lsass 424 42444 4008 7544 7824 15870 >> >> > 14 >> >> > 56 >> >> > svchost 640 19680 1096 888 944 2992 >> >> > 2 >> >> > 35 >> >> > svchost 704 22204 2508 1584 1632 7102 >> >> > 20 >> >> > 40 >> >> > svchost 768 41256 1580 3932 4000 7657 >> >> > 5 >> >> > 64 >> >> > svchost 804 26072 2184 4280 4328 6261 >> >> > 6 >> >> > 39 >> >> > svchost 820 169360 23508 24120 35276 365800 >> >> > 53 >> >> > 170 >> >> > spoolsv 952 29924 3552 3940 4524 53473 >> >> > 4 >> >> > 44 >> >> > msdtc 976 25448 520 1940 1988 1581 >> >> > 16 >> >> > 40 >> >> > BackupClientService 1104 82164 7268 10380 21296 59046490 >> >> > 5 >> >> > 76 >> >> > svchost 1180 17204 200 576 600 603 >> >> > 2 >> >> > 33 >> >> > sqlservr 1252 1787020 33992 77384 78664 430705 >> >> > 173 >> >> > 107 >> >> > svchost 1328 7232 200 304 332 388 >> >> > 1 >> >> > 15 >> >> > snmp 1376 42760 1588 3928 4492 11500 >> >> > 7 >> >> > 65 >> >> > SQBCoreService 1424 66812 1116 6976 33140 412501 >> >> > 5 >> >> > 67 >> >> > mqsvc 1912 38220 288 3404 3620 2019 >> >> > 129 >> >> > 63 >> >> > mssearch 1968 34060 440 5632 5656 3246 >> >> > 4 >> >> > 56 >> >> > sqlagent 1528 43896 1704 2624 2932 14570 >> >> > 4 >> >> > 63 >> >> > svchost 1656 33340 1208 2924 2972 1932 >> >> > 6 >> >> > 55 >> >> > svchost 1420 59652 2004 2600 23148 7049 >> >> > 5 >> >> > 59 >> >> > csrss 3060 22944 200 852 896 861 >> >> > 3 >> >> > 43 >> >> > winlogon 3084 33508 376 1608 2612 2586 >> >> > 4 >> >> > 60 >> >> > rdpclip 3216 33084 1608 1084 1100 3308 >> >> > 2 >> >> > 62 >> >> > explorer 3316 74268 10136 8396 10608 9787780 >> >> > 10 >> >> > 125 >> >> > BacsTray 3552 32400 608 896 908 2034 >> >> > 2 >> >> > 57 >> >> > BackupClient 3580 36216 1300 1636 1760 9540 >> >> > 2 >> >> > 59 >> >> > ctfmon 3612 26072 1876 596 896 10074 >> >> > 3 >> >> > 52 >> >> > sqlmangr 3620 37516 1136 1412 2800 2611 >> >> > 3 >> >> > 66 >> >> > wmiprvse 2524 27416 568 1844 2424 7816 >> >> > 3 >> >> > 45 >> >> > logon.scr 304 14144 220 344 344 653 >> >> > 1 >> >> > 29 >> >> > inetinfo 1004 48360 2012 3176 3376 8605 >> >> > 5 >> >> > 69 >> >> > NTRtScan 3464 148664 15184 13536 14444 1465266 >> >> > 12 >> >> > 78 >> >> > TmListen 1792 117584 9240 10872 14444 442991 >> >> > 43 >> >> > 102 >> >> > PccNTMon 676 45380 4184 3204 4500 73452 >> >> > 5 >> >> > 71 >> >> > TmPfw 1688 43840 1752 1408 2652 22065 >> >> > 5 >> >> > 65 >> >> > CNTAoSMgr 3780 21860 552 1132 1144 1057 >> >> > 2 >> >> > 31 >> >> > TmProxy 2728 30676 272 1692 4324 6801 >> >> > 34 >> >> > 37 >> >> > cmd 4732 13996 704 1476 1532 646 >> >> > 1 >> >> > 27 >> >> > wuauclt 4720 33960 3860 2012 2044 1119 >> >> > 3 >> >> > 63 >> >> > wmiprvse 632 29332 5356 2240 2712 1452 >> >> > 3 >> >> > 47 >> >> > pslist 5928 27520 2684 1000 1016 811 >> >> > 2 >> >> > 47 >> >> > >> >> > According to MS AWE should not be enabled on servers with 4 GB or >> >> > less. >> >> > However I have tried it and it did not solve the problem. >> >> > >> >> >> based on what i've seen so far this looks pretty normal. >> >> > >> >> > We have about 15 other DB servers and believe me this is not normal. >> >> > Below >> >> > is a listing of another DB server. Both servers have 4 Gb memory, >> >> > and >> >> > both >> >> > have the /PAE and the /3Gb enabled. >> >> > >> >> > Name Pid VM WS Priv Priv Pk Faults >> >> > NonP >> >> > Page >> >> > Idle 0 0 28 0 0 0 >> >> > 0 >> >> > 0 >> >> > System 4 1940 240 0 0 12730350 >> >> > 0 >> >> > 0 >> >> > smss 328 3548 480 128 168 371 >> >> > 0 >> >> > 6 >> >> > csrss 376 29212 4748 1880 1988 8220 >> >> > 6 >> >> > 83 >> >> > winlogon 404 60612 8284 9672 12332 100872 >> >> > 43 >> >> > 97 >> >> > services 452 61212 24436 4304 12256 54017 >> >> > 13 >> >> > 107 >> >> > lsass 464 50288 9196 8596 8664 6642 >> >> > 20 >> >> > 64 >> >> > svchost 696 19420 2788 864 944 871 >> >> > 2 >> >> > 35 >> >> > svchost 748 22116 3572 1376 1464 1157 >> >> > 20 >> >> > 39 >> >> > svchost 812 43088 4660 3912 4028 3641 >> >> > 6 >> >> > 64 >> >> > svchost 848 25772 5776 3752 3800 2081 >> >> > 6 >> >> > 39 >> >> > svchost 864 149772 33392 25972 45392 2100416 >> >> > 55 >> >> > 167 >> >> > spoolsv 996 29648 5912 4012 4520 12835 >> >> > 4 >> >> > 43 >> >> > msdtc 1020 24540 4476 1868 1916 1214 >> >> > 5 >> >> > 38 >> >> > BackupClientService 1156 73456 11544 7860 16192 59648100 >> >> > 5 >> >> > 76 >> >> > cimntfy 1172 32236 3632 1116 1132 923 >> >> > 3 >> >> > 54 >> >> > cissesrv 1196 7084 1424 260 284 53300 >> >> > 1 >> >> > 15 >> >> > cpqrcmc 1208 7336 1324 280 284 329 >> >> > 1 >> >> > 15 >> >> > vcagent 1224 32088 6996 2328 2496 1887 >> >> > 2 >> >> > 53 >> >> > svchost 1256 17204 2224 576 600 600 >> >> > 2 >> >> > 33 >> >> > inetinfo 1336 49312 8944 3376 5408 12618 >> >> > 5 >> >> > 69 >> >> > sqlservr 1424 1833320 1783240 1745952 1746948 1321535 >> >> > 19 >> >> > 126 >> >> > svchost 1568 13844 2624 936 936 1197 >> >> > 2 >> >> > 23 >> >> > snmp 1596 56960 4372 10720 12880 27825 >> >> > 9 >> >> > 81 >> >> > SQBCoreService 1656 67832 9708 6964 34428 316306 >> >> > 5 >> >> > 67 >> >> > sysdown 1768 10608 1480 336 336 366 >> >> > 1 >> >> > 21 >> >> > smhstart 1784 17408 3248 1344 1344 811 >> >> > 2 >> >> > 28 >> >> > hpsmhd 1920 39504 11116 7468 7944 33429 >> >> > 246 >> >> > 66 >> >> > cpqnimgt 2044 50688 6396 3484 4064 1629 >> >> > 4 >> >> > 70 >> >> > cqmgserv 2100 36256 4976 3576 3576 866074 >> >> > 5 >> >> > 55 >> >> > cqmgstor 2120 27864 4524 3704 3772 1164 >> >> > 7 >> >> > 47 >> >> > mssearch 2144 34056 1300 4136 4168 1976 >> >> > 4 >> >> > 56 >> >> > wmiprvse 2284 30548 6588 3100 4908 2950 >> >> > 3 >> >> > 45 >> >> > svchost 2332 32480 7760 5020 6984 7952 >> >> > 5 >> >> > 39 >> >> > rotatelogs 2500 20872 1940 620 620 494 >> >> > 1 >> >> > 40 >> >> > rotatelogs 2508 20872 1916 612 612 488 >> >> > 1 >> >> > 40 >> >> > hpsmhd 2552 105552 17224 14956 14968 37236 >> >> > 29 >> >> > 74 >> >> > cqmghost 2680 42852 7052 3420 3640 9972022 >> >> > 6 >> >> > 66 >> >> > rotatelogs 2720 20872 1948 620 620 496 >> >> > 1 >> >> > 40 >> >> > rotatelogs 2728 20872 1924 612 612 490 >> >> > 1 >> >> > 40 >> >> > sqlagent 2880 45432 3304 2684 2972 5495 >> >> > 5 >> >> > 63 >> >> > svchost 4004 33596 4028 2956 3028 1082 >> >> > 6 >> >> > 55 >> >> > svchost 1520 58372 4808 2596 23100 8265 >> >> > 5 >> >> > 59 >> >> > wmiprvse 4316 46964 8488 4888 5368 308082 >> >> > 5 >> >> > 69 >> >> > explorer 4936 74976 15992 7972 9648 9136526 >> >> > 11 >> >> > 128 >> >> > cpqteam 5004 26064 2636 612 612 793 >> >> > 1 >> >> > 49 >> >> > jusched 5016 38044 5836 1564 1584 1654 >> >> > 5 >> >> > 70 >> >> > BackupClient 5032 37256 3020 1716 1820 4704 >> >> > 2 >> >> > 61 >> >> > ctfmon 5052 17544 4608 528 896 1602 >> >> > 3 >> >> > 34 >> >> > sqlmangr 5060 38556 5340 1464 2852 2393 >> >> > 3 >> >> > 67 >> >> > csrss 4044 22940 2612 896 944 974 >> >> > 3 >> >> > 43 >> >> > winlogon 4720 33508 5008 1660 1732 1688 >> >> > 4 >> >> > 60 >> >> > rdpclip 5664 32828 3992 1040 1072 1322 >> >> > 2 >> >> > 61 >> >> > logon.scr 5080 14144 1656 344 344 447 >> >> > 1 >> >> > 29 >> >> > NTRtScan 4708 95236 16820 11680 12652 1264245 >> >> > 9 >> >> > 68 >> >> > TmListen 4900 117660 17472 10264 12700 229087 >> >> > 43 >> >> > 102 >> >> > PccNTMon 1028 47428 7880 3208 4504 35788 >> >> > 5 >> >> > 71 >> >> > TmPfw 4884 43836 5420 1408 2636 11105 >> >> > 5 >> >> > 65 >> >> > CNTAoSMgr 5676 21856 2652 1132 1144 685 >> >> > 2 >> >> > 31 >> >> > TmProxy 5884 30676 5132 1452 2764 2914 >> >> > 34 >> >> > 37 >> >> > w3wp 584 40276 6892 3604 3632 2835 >> >> > 7 >> >> > 45 >> >> > wuauclt 2056 34468 3976 2044 2044 1137 >> >> > 3 >> >> > 63 >> >> > >> >> > IF you compare the SQLServer prcess you can see that on the "good" >> >> > server >> >> > the physical memory used is around 1.7 GB however on the "bad" >> >> > server >> >> > it >> >> > is >> >> > only 33 MB >> >> > >> >> > sqlservr 1424 1833320 1783240 1745952 1746948 1321535 >> >> > 19 >> >> > 126 >> >> > sqlservr 1252 1787020 33992 77384 78664 >> >> > 430705 >> >> > 173 107 >> >> > >> >> > My guess is that SQL is not the problem here. If I shut down SQL >> >> > server >> >> > I >> >> > only get around 33 MB back. Something is eating my physical memory >> >> > and >> >> > it >> >> > is >> >> > not showing up in any program or taskmanager.
Recommended Posts