Sponsored Content
Full Discussion: Scan Rates
Operating Systems AIX Scan Rates Post 302307784 by zaxxon on Thursday 16th of April 2009 10:29:18 AM
Old 04-16-2009
3k pages as scan rate per sec is no big value. I sometimes see bigger ones. Usually it's the ratio/relation between scanned pages and freed pages that matters. Optimal to ok should be ratio fr/sr of ~ 1:1 - 1:3 afaik; can be but must not.

From some IBM AIX Performance Management Guide, note the last line in bold letters:
Quote:
# fr

Number of pages that were freed per second by the page-replacement algorithm during the interval. As the VMM page-replacement routine scans the Page Frame Table (PFT), it uses criteria to select which pages are to be stolen to replenish the free list of available memory frames. The criteria include both kinds of pages, working (computational) and file (persistent) pages. Just because a page has been freed, it does not mean that any I/O has taken place. For example, if a persistent storage (file) page has not been modified, it will not be written back to the disk. If I/O is not necessary, minimal system resources are required to free a page.
# sr

Number of pages that were examined per second by the page-replacement algorithm during the interval. The VMM page-replacement code scans the PFT and steals pages until the number of frames on the free list is at least the maxfree value. The page-replacement code might have to scan many entries in the PFT before it can steal enough to satisfy the free list requirements. With stable, unfragmented memory, the scan rate and free rate might be nearly equal. On systems with multiple processes using many different pages, the pages are more volatile and disjoint. In this scenario, the scan rate might greatly exceed the free rate.

Memory is over committed when the ratio of fr to sr (fr:sr) is high.

An fr:sr ratio of 1:4 means that for every page freed, four pages had to be examined. It is difficult to determine a memory constraint based on this ratio alone, and what constitutes a high ratio is workload/application dependent.

For tuning in general and to get a first impression, you should look at the output from "vmstat 1 20" for example at busy times. Just looking at "sr" will show/mean nothing.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

IP Name scan

Hi. how to search a range of IP:s for their registed IP names? Like nslookup or host for all IPs 130.xxx.xxx.1 to 130.xxx.xxx.254 //nicke (2 Replies)
Discussion started by: nicke30
2 Replies

2. Advertise with Us

Special Discount Rates for Job Posting In Effect

The UNIX and Linux Job Board is a service provided by the The UNIX and Linux Forums to help employers connect with UNIX and Linux professionals. All proceeds from this service go towards supporting the forums. Please PM Neo or email with any questions about this service. Promotion A: $99 ... (0 Replies)
Discussion started by: Neo
0 Replies

3. Shell Programming and Scripting

FTP run from shell script gives slow transfer rates

Hey everybody, this is my first post so be gentle. I have two Sun 5220's running Solaris 10 that are directly connected with a cross-over cable at Gig. One of these boxes is my production Oracle server which generates a 50GB dump file every evening at 10:50. The other Solaris is a devolopment... (8 Replies)
Discussion started by: Countificus
8 Replies

4. What is on Your Mind?

Where to find higher consulting rates?

Have any IT consultants here been on a project where you knew the bill rate was really high but you only got a tiny piece of it (like paid $60/hr and billed out around $200)? Does anyone know of a company that pays consultants well - like 70-80% or more of what they're getting? (5 Replies)
Discussion started by: apierce
5 Replies

5. Cybersecurity

Virus/Malware Uptake Rates

Hi. I'm trying to get information about the rates at which viruses and malware infect computers. Let's say that Mr. Dastardly Developer discovers an exploitable flaw, writes a virus to take advantage of it, and releases the virus. Assuming that a large-scale attack method is chosen (Facebook,... (2 Replies)
Discussion started by: treesloth
2 Replies

6. Hardware

BackBlaze article on HDD failure rates.

Very interesting. One for the pros here... Hard Drive Failure Rates: The Results from 68,813 Hard Drives (3 Replies)
Discussion started by: wisecracker
3 Replies
ALLOC_HUGEPAGES(2)					     Linux Programmer's Manual						ALLOC_HUGEPAGES(2)

NAME
alloc_hugepages, free_hugepages - allocate or free huge pages SYNOPSIS
void *alloc_hugepages(int key, void *addr, size_t len, int prot, int flag); int free_hugepages(void *addr); DESCRIPTION
The system calls alloc_hugepages() and free_hugepages() were introduced in Linux 2.5.36 and removed again in 2.5.54. They existed only on i386 and ia64 (when built with CONFIG_HUGETLB_PAGE). In Linux 2.4.20, the syscall numbers exist, but the calls fail with the error ENOSYS. On i386 the memory management hardware knows about ordinary pages (4 KiB) and huge pages (2 or 4 MiB). Similarly ia64 knows about huge pages of several sizes. These system calls serve to map huge pages into the process's memory or to free them again. Huge pages are locked into memory, and are not swapped. The key argument is an identifier. When zero the pages are private, and not inherited by children. When positive the pages are shared with other applications using the same key, and inherited by child processes. The addr argument of free_hugepages() tells which page is being freed: it was the return value of a call to alloc_hugepages(). (The memory is first actually freed when all users have released it.) The addr argument of alloc_hugepages() is a hint, that the kernel may or may not follow. Addresses must be properly aligned. The len argument is the length of the required segment. It must be a multiple of the huge page size. The prot argument specifies the memory protection of the segment. It is one of PROT_READ, PROT_WRITE, PROT_EXEC. The flag argument is ignored, unless key is positive. In that case, if flag is IPC_CREAT, then a new huge page segment is created when none with the given key existed. If this flag is not set, then ENOENT is returned when no segment with the given key exists. RETURN VALUE
On success, alloc_hugepages() returns the allocated virtual address, and free_hugepages() returns zero. On error, -1 is returned, and errno is set appropriately. ERRORS
ENOSYS The system call is not supported on this kernel. FILES
/proc/sys/vm/nr_hugepages Number of configured hugetlb pages. This can be read and written. /proc/meminfo Gives info on the number of configured hugetlb pages and on their size in the three variables HugePages_Total, HugePages_Free, Hugepagesize. CONFORMING TO
These calls are specific to Linux on Intel processors, and should not be used in programs intended to be portable. NOTES
These system calls are gone; they existed only in Linux 2.5.36 through to 2.5.54. Now the hugetlbfs filesystem can be used instead. Mem- ory backed by huge pages (if the CPU supports them) is obtained by using mmap(2) to map files in this virtual filesystem. The maximal number of huge pages can be specified using the hugepages= boot parameter. COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2017-09-15 ALLOC_HUGEPAGES(2)
All times are GMT -4. The time now is 12:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy