|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Today @ 6:13 PM
Points: 312,
Visits: 1,871
|
|
All,
We have some performance issue..SQL server is running very slow due to high memory usage..this is a 2 node active/passive cluster. Only 1 instance is running, no other apps.
Total 56GB RAM and 46GB is allocated SQL. No blocking, no open transactions, no long running queries found.
Is there any other way to release the memory? Or how can we find why SQL server is using high memory?
What are some of the causes of using high memory? Someone with experience in performance tuning, please advise.
Thanks, SueTons
|
|
|
|
|
SSCoach
         
Group: General Forum Members
Last Login: Yesterday @ 10:25 AM
Points: 18,754,
Visits: 12,337
|
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Today @ 5:04 PM
Points: 555,
Visits: 1,036
|
|
Can you elaborate on what you mean by SQL is running slow? Specifics? You state that it is slow but there are no long running queries found.
Joie Andrew "Since 1982"
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 3:18 PM
Points: 37,744,
Visits: 30,025
|
|
SQLCrazyCertified (1/3/2013) We have some performance issue..SQL server is running very slow due to high memory usage.
Are you sure that high memory usage is causing SQL to run slow? Cause, not correlation?
Is there any other way to release the memory? Or how can we find why SQL server is using high memory?
What are some of the causes of using high memory? Someone with experience in performance tuning, please advise.
Normal, expected behaviour. SQL uses as much memory as it is allowed to use to cache data and plans to avoid slow disk access and expensive plan recompilations. SQL will use up to the max it is allowed and that is perfectly fine. You typically want SQL to use lots of memory as it allows for efficient caching.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|
|
SSChampion
        
Group: General Forum Members
Last Login: Today @ 3:41 AM
Points: 13,383,
Visits: 25,189
|
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Today @ 6:13 PM
Points: 312,
Visits: 1,871
|
|
SQLRNNR, There are only 50 active connections.....so, I don't think this is the issue.
Joie Andrew, Had complains that everything is running slow and I coudn't find anything else other than SQL using all the memory which is allocated to it.
GilaMonster, I am not 100% sure if it's only memory related, however, I am stuck as to what's the next step....not an exper on performance tuning.
Grant Fritchey, I did select * from sys.dm_os_wait_stats, now which column should I focus.
I really appreciate all of you for giving me valid inputs as to where/what should I be checking. Could this be a CPU issue as well?
Thanks, SueTons.
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 3:18 PM
Points: 37,744,
Visits: 30,025
|
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Today @ 6:13 PM
Points: 312,
Visits: 1,871
|
|
Is there any other way to release the memory? Or how can we find why SQL server is using high memory?
What are some of the causes of using high memory? Someone with experience in performance tuning, please advise.
Normal, expected behaviour. SQL uses as much memory as it is allowed to use to cache data and plans to avoid slow disk access and expensive plan recompilations. SQL will use up to the max it is allowed and that is perfectly fine. You typically want SQL to use lots of memory as it allows for efficient caching. [/quote]
Gail,
You mentioned that SQL using all of it's memory which is allocated to it is a normal behavior, if this is true, when does the SQL release the memory?
I know it won't release the memory to OS, but when does SQL gets more memory to do other work/processes. Please advise.
SueTons.
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 3:18 PM
Points: 37,744,
Visits: 30,025
|
|
SQLCrazyCertified (1/4/2013) You mentioned that SQL using all of it's memory which is allocated to it is a normal behavior, if this is true, when does the SQL release the memory?
When the OS signals that it's under memory pressure or when SQL shuts down.
I know it won't release the memory to OS, but when does SQL gets more memory to do other work/processes. Please advise.
Get more memory? If it's allocated up to max server memory then it won't allocate more.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Today @ 6:13 PM
Points: 312,
Visits: 1,871
|
|
GilaMonster (1/5/2013)
SQLCrazyCertified (1/4/2013) You mentioned that SQL using all of it's memory which is allocated to it is a normal behavior, if this is true, when does the SQL release the memory?When the OS signals that it's under memory pressure or when SQL shuts down. I know it won't release the memory to OS, but when does SQL gets more memory to do other work/processes. Please advise. Get more memory? If it's allocated up to max server memory then it won't allocate more.
So, if I understand you correctly, if SQL uses all the memory which is allocated to it, then SQL will not have enough memory to work on other outstanding processes, so, in this scenario can we say that memory is the issue for performance issues? If that's the case how can you say it's the normal expected behavior?
SueTons.
|
|
|
|