PF usage Problem

Question

Post reply

PF usage Problem

Viewing 12 posts - 16 through 26 (of 26 total)

You must be logged in to reply to this topic. Login to reply

dm_tapas Hall of Fame Points: 3515 More actions · Answer 1

Go for it :

EXEC sp_configure 'max server memory (MB)', 26624 --26 GB

GO

RECONFIGURE

GO

dm_tapas Hall of Fame Points: 3515 More actions · Answer 2

Go for it :

EXEC sp_configure 'max server memory (MB)', 26624 --26 GB

GO

RECONFIGURE

GO

MasterDB Hall of Fame Points: 3054 More actions · Answer 3

After setting Max server memory to 28 GB still in the Task manager PFusage is showing as 29.7GB.

Ninja's_RGR'us SSC Guru Points: 294069 More actions · Answer 4

@Gail, take over from here. Getting outside my confort zone and no time to research.

Usman Butt Hall of Fame Points: 3186 More actions · Answer 5

Ninja's_RGR'us (11/1/2011)
@Gail, take over from here. Getting outside my confort zone and no time to research.

You are indeed outside your confort oops.. comfort zone. 🙂 just kidding, please do not mind.

I think the PF would not be released until a restart occurs.

Final words should be from our GURU @Gail.

Ninja's_RGR'us SSC Guru Points: 294069 More actions · Answer 6

Usman Butt (11/1/2011)
Ninja's_RGR'us (11/1/2011)
@Gail, take over from here. Getting outside my confort zone and no time to research.
You are indeed outside your confort oops.. comfort zone. 🙂 just kidding, please do not mind.
I think the PF would not be released until a restart occurs.
Final words should be from our GURU @Gail.

My default answer here would be to reboot so that everything gets reset, but usually there's a less drastic solution.

And since Gail pretty much only works in 24/7 system, she knows that info already without further research.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 7

MasterDB (11/1/2011)
Ninja:i set max server memory for SQL is 40722MB

So you've told SQL Server to use 40GB out of the available 32 GB. See the problem with that?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 8

MasterDB (11/1/2011)
After setting Max server memory to 28 GB still in the Task manager PFusage is showing as 29.7GB.

Task manager = pile of lies. Plus what it shows and what that means changes depending on the OS.

Are you seeing paging? (hint, perfmon not task manager)

Are you seeing a performance problem?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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

MasterDB Hall of Fame Points: 3054 More actions · Answer 9

Hi,

I ran perfmon , in that am not able to find the paging in the .csv file.

please can u explain how to check the paging through perfmon.

Exactly it is not a performance problem, when the Pf usage goes very high nobody able to connect SQL SERVER after restarting SQL Services then PF usage becomes normal for sometime everything goes normal and later again am facing the same problem.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 10

MasterDB (11/2/2011)
I ran perfmon , in that am not able to find the paging in the .csv file.
please can u explain how to check the paging through perfmon.

Paging file % usage perhaps?

http://www.brentozar.com/archive/2006/12/dba-101-using-perfmon-for-sql-performance-tuning/

Also Available Memory (MB), mustn't drop below a couple hundred (some say 1GB)

Exactly it is not a performance problem, when the Pf usage goes very high nobody able to connect SQL SERVER after restarting SQL Services then PF usage becomes normal for sometime everything goes normal and later again am facing the same problem.

I'm going to assume you're using Server 2003 (because Server 2008 doesn't have a task manager entry as you describe)

In server 2003 what task manager lists as PF Usage is actually the system commit charge - the total amount of memory in use. Now, with the memory settings that you had, where SQL was allowed to use 8GB more memory than actually existed, you will get connection problems, SQL would happily take all the memory on the server (as it was allowed to do) and leave nothing for the OS. That is fixed now that max server memory has been dropped to below the actual amount of memory that exists.

This connection problem should hence be fixed. If it happens again, you'll need to get a lot more data around what's happening on the server, and preferably not with Task Manager

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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

MasterDB Hall of Fame Points: 3054 More actions · Answer 11

Thanks for your suggestion dude...

that really helps me...

seriously you are master.....:-)

Ninja's_RGR'us SSC Guru Points: 294069 More actions · Answer 12

MasterDB (11/2/2011)
Thanks for your suggestion dude...
that really helps me...
seriously you are master.....:-)

She's definitely one the the prettiest dude I know :-D.