When it comes to the System memory , there are 3 things to monitor :
1.Monitor Cache (Hits/Misses),
2.Monitor Memory (Memory Available/sec, Process/Working Set),
3.Monitor Paging (Pages Read/Sec, Pages Input/Sec, Page Faults/Sec, % Disk Processing)
Memory\Available Bytes, if this counter is greater than 10% of the actual RAM in your machine then you probably have more than enough RAM and don't need to worry.
The Memory\Pages/sec counter indicates the number of paging operations to disk during the measuring interval, and this is the primary counter to watch for indication of possible insufficient RAM to meet your server's needs.
You can monitor Process(instance)\Working Set for each process instance to determine which process is consuming larger and larger amounts of RAM. Process(instance)\Working Set measures the size of the working set for each process, which indicates the number of allocated pages the process can address without generating a page fault. A related counter is Memory\Cache Bytes, which measures the working set for the system i.e. the number of allocated pages kernel threads can address without generating a page fault.
Finally, another corroborating indicator of insufficient RAM is Memory\Transition Faults/sec, which measures how often recently trimmed page on the standby list are re-referenced. If this counter slowly starts to rise over time then it could also indicating you're reaching a point where you no longer have enough RAM for your server to function well.
1.Monitor Cache (Hits/Misses),
2.Monitor Memory (Memory Available/sec, Process/Working Set),
3.Monitor Paging (Pages Read/Sec, Pages Input/Sec, Page Faults/Sec, % Disk Processing)
Memory\Available Bytes, if this counter is greater than 10% of the actual RAM in your machine then you probably have more than enough RAM and don't need to worry.
The Memory\Pages/sec counter indicates the number of paging operations to disk during the measuring interval, and this is the primary counter to watch for indication of possible insufficient RAM to meet your server's needs.
You can monitor Process(instance)\Working Set for each process instance to determine which process is consuming larger and larger amounts of RAM. Process(instance)\Working Set measures the size of the working set for each process, which indicates the number of allocated pages the process can address without generating a page fault. A related counter is Memory\Cache Bytes, which measures the working set for the system i.e. the number of allocated pages kernel threads can address without generating a page fault.
Finally, another corroborating indicator of insufficient RAM is Memory\Transition Faults/sec, which measures how often recently trimmed page on the standby list are re-referenced. If this counter slowly starts to rise over time then it could also indicating you're reaching a point where you no longer have enough RAM for your server to function well.
11 comments:
This is an awesome piece. Didnt know that Scott Barbers exist in india too. I am working in performance engineering in Symphony Services. Would like to know if any books on performance management.
Krishna,
You can refer to Daniel Menasce's books(about 3 to 4 excellent books are there) available on Capacity Planning. But with reference to Performance testing there are not specific books available. You can refer to Scott Barber's blog where he has published a book on Performance testing.
Great Work
Which tools did you use in your measurememtns?
Gurugale...
Awesome Information on Analysis, also please suggest me to improve with Analysis practically am facing it difficult with the server graphs to analyze.Suggest me some books or examples of analyzing server graphs.
Currently working on LoadRunner in Nuware Systems.
Thanks
Chandru
Hi Chandru,
The best book on Analysis which i know is "The Art of Computer Systems Performance Analysis".
try this..
-ranga
Hi Ramya,
Plz write the real time bottlenecks in ur blog , beginners can easily understand the bottlenecks and also mention the Acceptance criteria for counters for Web server,Application server, Database server, Client machine and also put in ur blog some templete like defect report, Test plan, summary report. these are all helps to all who are visiting the blog.if u prepared the load runner tutorial how to use.
Lots of thanks...... for very nice blog.
Thanks and regards,
Ramamurthy
Hi Ramya,
Plz write the real time bottlenecks in ur blog , beginners can easily understand the bottlenecks and also mention the Acceptance criteria for counters for Web server,Application server, Database server, Client machine and also put in ur blog some templete like defect report, Test plan, summary report. these are all helps to all who are visiting the blog.if u prepared the load runner tutorial how to use.
Lots of thanks...... for very nice blog.
Thanks and regards,
Ramamurthy
i did not see any thing related to performance testing in cloud..
Now a days most of the organizations trying to move to cloud..
Think we should start in this are too
hey
just registered and put on my todo list
hopefully this is just what im looking for looks like i have a lot to read.
Great post!, i am looking at differences in memory management for Unix and Windows box, might be good topic
Post a Comment