{"id":5672,"date":"2018-08-23T09:45:57","date_gmt":"2018-08-23T14:45:57","guid":{"rendered":"https:\/\/www.poweradmin.com\/blog\/?p=5672"},"modified":"2018-09-13T13:29:48","modified_gmt":"2018-09-13T18:29:48","slug":"pages-per-second-counters","status":"publish","type":"post","link":"https:\/\/www.poweradmin.com\/blog\/pages-per-second-counters\/","title":{"rendered":"Pages Per Second Counters"},"content":{"rendered":"

By Zo\u00eb Dunning<\/span><\/strong><\/span><\/p>\n

\u00a0<\/p>\n

Continuing with last week\u2019s article on Current and Average Disk Queue Length, this week we\u2019ll discuss <\/span>Pages Per Second<\/strong> and its related counters.<\/span><\/p>\n

Overview<\/strong><\/span><\/h2>\n

Just as you should monitor the number of requests that Current and Avg. Disk Queue Length represent in the queue to pinpoint possible bottleneck, you should also keep an eye on the Pages Per Second counter to determine whether you are at risk of the memory system becoming limited or diminished.<\/span><\/p>\n

\u00a0<\/p>\n

\u201c\\Memory\\Pages\/sec\u201d <\/strong>is based on the combined input and output of pages, also referred to as the \u201c\\Memory\\Pages Input\/sec\u201d<\/strong> and \u201c\\Memory\\Pages Output\/sec\u201d<\/strong> counters. Pages Input\/sec is the total number of pages read from the disk, and Pages Output\/sec represents the total number of pages removed from memory and traveling toward the disk. My Pages Output\/sec is so low that it doesn\u2019t show on the graph below, being flatlined.<\/span><\/p>\n

\u00a0<\/p>\n

\"\"<\/a><\/p>\n

Pink<\/span>= Pages Input\/sec; Blue<\/span>= Pages Output\/sec<\/span><\/p>\n

\u00a0<\/p>\n

Closely related to Pages\/sec are the \u201c\\Memory\\Page Reads\/sec\u201d <\/strong>and \u201c\\Memory\\Page Writes\/sec\u201d<\/strong> counters, as they show how much the disk is affected by paging operations. Page Reads\/sec is the rate at which the disk is read to resolve page faults. Page Writes\/sec is the rate at which page data is written to the disk to open up space in physical memory.<\/span><\/p>\n

\u00a0<\/p>\n

\"\"<\/a><\/p>\n

Green<\/span>= Page Reads\/sec; Yellow<\/span>= Page Writes\/sec<\/span><\/p>\n

Potential Problems<\/strong><\/span><\/h2>\n

Memory is frequently the root cause of performance problems. Thus, you should rule out memory problems accordingly before examining other system areas for potential sources.<\/span><\/p>\n

\u00a0<\/p>\n

The lower the memory system\u2019s paging values, the better. Even if they spike occasionally, you have no cause for concern if they soon return to the same values (or approximations). However, if your Pages Input\/sec counter shows a value of 20 or greater<\/u> for a slow disk, you should closely monitor it. A faster disk should be able to process more. If your Pages\/sec counter consistently shows more than 40 pages per second<\/u> on a slow disk or 300 pages per second<\/u> on a fast disk, you should investigate. Your system memory is\u2014in all likelihood\u2014too small for the processing load.<\/span><\/p>\n

\u00a0<\/p>\n

Page faults<\/strong> are one of the most common memory-related bottleneck issues encountered with paging operations that can be monitored by Pages\/sec and its associated memory counters. A page fault results when a process requests a page in memory, but the system can\u2019t recover it from the requested location. The page fault is placed in a \u201cwait\u201d state while the operating system attempts to restore that page to physical memory. If the requested page is still in memory but perhaps in the wrong process, this is a soft fault. On the other hand, if the page must be retrieved from the disk, this is a hard fault. Most processors can manage soft faults, but hard faults can instigate substantial delays.<\/span><\/p>\n

\u00a0<\/p>\n

The \u201c\\Memory\\Page faults\/sec\u201d <\/strong>counter, shown below, monitors the rate at which the processor handles both soft and hard faults. As you can see, my rate of page faults is skyrocketing. If my Page reads\/sec were also high, that would be a strong indicator of insufficient RAM<\/strong>.\u00a0<\/span><\/p>\n

\u00a0<\/p>\n

\"\"<\/a><\/p>\n

Red<\/span>= Page Faults\/sec; Green<\/span>= Pages\/sec<\/span><\/p>\n

Troubleshooting<\/strong><\/span><\/h2>\n

If your Pages Input\/sec counter shows a value of 20 or greater<\/u> for a slow disk and\/or your Pages\/sec counter consistently shows more than 40 pages per second<\/u> on a slow disk or 300 per second<\/u> on a fast disk, you can solve this issue simply by adding more memory to your server.<\/span><\/p>\n

\u00a0<\/p>\n

To discover whether or not you\u2019re experiencing hard page faults, compare your values of Pages Input\/sec and Page Reads\/sec to determine the average number of pages read into memory during every operation. Pages Input\/sec will be greater than or equal to Page Reads\/sec if you have hard faults (see below). A large quantity of hard page faults could signify that you need to increase the amount of memory or reduce the cache size on the server.<\/span><\/p>\n

\u00a0<\/p>\n

\"\"<\/a><\/p>\n

Green<\/span>= Page Reads\/sec; Pink<\/span>= Pages Input\/sec<\/span><\/p>\n

Conclusion<\/strong><\/span><\/h2>\n

\u201c\\Memory\\Pages\/sec\u201d is the sum of \u201c\\Memory\\Pages Input\/sec\u201d and \u201c\\Memory\\Pages Output\/sec\u201d. Pages Input\/sec is the total number of pages read from the disk, and Pages Output\/sec is the total number of pages sent to disk from memory. \u201c\\Memory\\Page Reads\/sec\u201d and \u201c\\Memory\\Page Writes\/sec\u201d show how much the disk is affected by paging operations based on the rate that pages that are read and written to the disk. \u201c\\Memory\\Page faults\/sec\u201d is the rate at which the processor handles both soft and hard faults.<\/span><\/p>\n

\u00a0<\/p>\n

Memory is usually the source of performance problems, so check it first before another system area. The lower the memory system\u2019s paging values, the better. If your Pages Input\/sec and Pages\/sec counters show irregularly high values consistently, you can resolve the issue by adding more memory to your server.<\/span><\/p>\n

\u00a0<\/p>\n

Page faults\u2014when a process requests a page in memory, but the system can\u2019t recover it\u2014can be soft or hard, but you mainly have to worry about hard faults. Pages Input\/sec will be greater than or equal to Page Reads\/sec if you have hard faults. For this problem, the solution is to increase the server\u2019s memory or reduce the cache size. Finally, if your Page Faults\/sec and Page Reads\/sec are both high, you could have insufficient RAM.<\/span><\/p>\n

\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"

By Zo\u00eb Dunning \u00a0 Continuing with last week\u2019s article on Current and Average Disk Queue Length, this week we\u2019ll discuss Pages Per Second and its related counters. Overview Just as you should monitor the number of requests that Current and Avg. Disk Queue Length represent in the queue to pinpoint possible bottleneck, you should also […]<\/p>\n","protected":false},"author":15,"featured_media":5710,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,5,57,8],"tags":[63,75,59,78,76,77,73,74,66,56,64,62],"class_list":["post-5672","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-general-it","category-how-to","category-monitoring","category-windows","tag-counters","tag-memory","tag-monitoring","tag-page-faults-per-second","tag-page-reads-per-second","tag-page-writes-per-second","tag-pages-input-per-second","tag-pages-output-per-second","tag-pages-per-second","tag-performance-monitor","tag-troubleshooting","tag-windows"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/5672","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/comments?post=5672"}],"version-history":[{"count":4,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/5672\/revisions"}],"predecessor-version":[{"id":5696,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/5672\/revisions\/5696"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/media\/5710"}],"wp:attachment":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/media?parent=5672"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/categories?post=5672"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/tags?post=5672"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}