Performance Issue

[abit]

Hi all!! and after all, sorry for my english!!!

We have a memory problem, that I don't know how to solve.
We have a Windows Server 2008 Enterprise with 8 cores and 32Gb of RAM.
We assign 20GB to SQL Server, an there is 12 GB free for OS.

Basically the problem is that Windows Server is out of memory.

For example statistics (we have to restart the server to get it normal again):
Total Memory 32GB
Used for SQL Server 20GB
Cached memory 10GB What means that, the OS use this memory???
Free Memory 512MB !!!!!!!!!

I don't know what means Cached Memory for Windows Server, but when we get out of memory the performace of the server is very bad.

I ask here becouse, I thinks there would be someone who got the same problem, but i will ask in a windows server forum too.

Thanks for all!!! and sorry for my english

 

[ICTCity]

Hi there,

Unlucky this is a know-issue with x64 systems.

The problem seems to be SQL, I can just suggest you to download this:

http://www.microsoft.com/downloads/...0a-5efe-43c8-b9c3-5d0ecb2f39af&displaylang=en

***PLEASE BE SURE TO READ AND UNDERSTAND WHAT'S WRITTEN IN THE ATTACHED DOCUMENT (README.DOCX)***

let me know if you need further help.

 

[abit]

Hi there,

Unlucky this is a know-issue with x64 systems.

The problem seems to be SQL, I can just suggest you to download this:

http://www.microsoft.com/downloads/...0a-5efe-43c8-b9c3-5d0ecb2f39af&displaylang=en

***PLEASE BE SURE TO READ AND UNDERSTAND WHAT'S WRITTEN IN THE ATTACHED DOCUMENT (README.DOCX)***

let me know if you need further help.

thanks so much!!
are you sure that the problem is SQL? (you say seems)

Sorry but I have a little kwonleage of Windows Server, and I would like to know what is and what does Windows do with cached memory.

If I put more RAM, the problem will solve, do you that? or the cached memory will grow without limits.

It's big problem for us this "issue"

thanks for your help.

 

[ICTCity]

It's not only with Sql... But it's not windows itself.

Anyway, before using the procedure go to SQL manager and be sure that under memory you don't have AWE checked.

Let me know

 

[abit]

It's not only with Sql... But it's not windows itself.

Anyway, before using the procedure go to SQL manager and be sure that under memory you don't have AWE checked.

Let me know

I'm sure that AWE is not checked.

I'm not in charge of Windows Server, but I'll tell my coworker about the link you post.

Thanks a lot.

I really can't believe that windows server enterprise behave that way.

 

[ICTCity]

I know it's quite unbelievable but this seems to be the hard truth. The problem should be HOW windows can allocate dynamic memory. It looks like windows can't free cached memory when not used. With the provided link you can manage this setting.

 

[abit]

I know it's quite unbelievable but this seems to be the hard truth. The problem should be HOW windows can allocate dynamic memory. It looks like windows can't free cached memory when not used. With the provided link you can manage this setting.

Thanks so much for the explanation, I will read more about the link you gave me and we will see what to do.
It's hard to believe to me because I don't find much info over the internet about it, and I think I'm not the only one with this issue.

 

[ICTCity]

You're not the only one. The main problem is that almost nobody understand WHO is the guilty. 6 Months ago I've set up SQL with server 2008, 16 GB and after 3 months I've upgraded to R2. I had the same issue but the AWE was enabled.

Anyway the situation was similar... I changed ram type and the problem went away!

 

[abit]

You're not the only one. The main problem is that almost nobody understand WHO is the guilty. 6 Months ago I've set up SQL with server 2008, 16 GB and after 3 months I've upgraded to R2. I had the same issue but the AWE was enabled.

Anyway the situation was similar... I changed ram type and the problem went away!

What do you mean with "I changed ram type"? sorry I don't understand.

thanks so much.

 

[ICTCity]

I mean change manufacturer. I had some faulty modules and I changed all in one time with Kingstone modules.

Anyway, I don't think the problem is hardware related, because after this change I also update our accounting software, which had in release note "Memory Management Improvement".

Cached memory is a feauture of Win 7 / 2k8. Programs are stored in RAM if there's space, this improve the speed of your system and your programs will open faster then before.

It's like CPU - Caching (L1,L2,L3,...), essentially it's the same thing. Now the problem is that what happens when a program is started. I don't know if your problem happens only with SQL or with another "external" problem. What I know is that some stored procedures / queries which need RAM, can cause Windows going out of memory! That's because you can set things as you want with the link I've provided before. Unless you want to investigate on WHAT it's really consuming your RAM.