when you have more processes then the real memory can accomodate.
the processes are swapped out to paging space a type of physcial storage.
page in and page out is common, but swapping is a problem.
CPU is utilized heavily during that swapping.
Bmujeeb, that is correct!
Dr_suresh20, the easyes way to find out if windows page-ing is present do the following:
1. Start Task Manager
2. Click on Performance tab
3. In Physical Memory frame there is "Available" - that is the available real memory
4. In Commit Charge frame there is "Total" - this is used memory
5. If the "Available" > "Total" then you have a windows page-ing problem.
If you have the windows pageing problem, then try to stop all the applications that are not needed. Also stop services that are not needed.
On database there is the most common mistake to overlocate the bufferpools. So if the total amount of bufferpools are bigger then the real memory try to lower the bufferpools.
Execute the db2 command:
select * from sysibm.sysbufferpools
to see the amount of usage bufferpools.
Then manualy calculate the BufferpoolUsageInBytes = NPAGES * PAGESIZE. If more then one bufferpool is defined then calculate the BufferpoolUsageInBytes and sum the results from each row.
So the optimal page size is 6 GB. My favorite setting is to create a windows partition e.g. F: which is in your case 10 GB in size and then define windows page file 6 GB on this partition. You have 4 GB on "page partition" just in case if you would like to increase the size (e.g. if new real memory is bought)
If page file is defined in seperate partition then no fragment of page file is present. So you do not need to defragment this partition on regular basis.
In window enviroment, my first step should be to stop the processes
which I don't need.window has this problem of starting too many processes
without needing them and most of these proceeses have multiple threads