Welcome to the blog site of SQLServer.in

VAS continued…

VAS continued…

Each process allocate VAS in the starting. As required, the VAS regions will be bind to the physical memory. This will be done by means of committing(using VirtualAlloc API), AWE mechanism, file mapping API’s etc.

Physical pages can be shared or private. If the same physical pages are shared accross different VAS, its called shared physical pages, else if only mapped to a single VAS, they are called private physical pages. The physical pages could be either in disk or ram. If its only from RAM, its referenced as working set or memory usage in windows task manager.

Working set shown in the perfrmon & task manger includes non private pages.

Working Set in Perfmon counter = Mem Usage in Task manager
Private Bytes in perfmon counter = Virtual Memory Size in Task Manager

1 Comment

  1. by Tweets that mention VAS continued... | SQLServer.in -- Topsy.com, on April 21 2010 @ 5:15 pm

     

    [...] This post was mentioned on Twitter by sqlserver. sqlserver said: New post: VAS continued… (http://bit.ly/9HOjsh) [...]

Comment RSS

Get Adobe Flash playerPlugin by wpburn.com wordpress themes
 

About Author

Krishna is a Senior Database Administrator, having handson experience of 6 years. Areas of expertise includes database engine, Business Intelligence & performance tunning. A regular SQL blogger on his own website, msdn forums, sqlteam.com & believe in sharing his experience with other technology enthusiasts.