9 More Discussions You Might Find Interesting
1. AIX
I have a IBM Power9 server coupled with a NVMe StorWize V7000 GEN3 storage, doing some benchmarks and noticing that single thread I/O (80% Read / 20% Write, common OLTP I/O profile) seems slow.
./xdisk -R0 -r80 -b 8k -M 1 -f /usr1/testing -t60 -OD -V
BS Proc AIO read% IO Flag IO/s ... (8 Replies)
Discussion started by: c3rb3rus
8 Replies
2. Tips and Tutorials
Overview:
Introduction
What Does Success Mean?
What Does Performance Mean?
Every Picture is Worth a Thousand Words
Work Like a Physicist
Work Like You Walk - One Step at a Time
Learn to Know Your System
Choose Your Weapons!
Tools of the Trade 1 - vmstat
A Little Theory Along the Way -... (1 Reply)
Discussion started by: bakunin
1 Replies
3. Solaris
Dear all,
I have a Local zone , where users feel that performance is not good.
Is it wise to collect the inputs from the local zone rather than taking from the global zone.
And also Can I tune from Global zone , so that it will reflect in local zone.
Rgds
rj (2 Replies)
Discussion started by: jegaraman
2 Replies
4. UNIX for Advanced & Expert Users
Hi,
I am facing a strange issue. Application is deployed in a cluster with 2 Unix nodes (with same configuration). On one node the application is working fine but on another node we see this behavior I found using vmstat- when the server is not yet started everything is OK; when you start the... (3 Replies)
Discussion started by: ash.abrol
3 Replies
5. Shell Programming and Scripting
Hi All,
In last one week, i have posted many questions in this portal. At last i am succeeded to make my 1st unix script.
following are 2 points where my script is taking tooooo long.
1. Print the total number of records excluding header & footer. I have found that awk 'END{print NR -... (2 Replies)
Discussion started by: Amit.Sagpariya
2 Replies
6. Shell Programming and Scripting
Sorry,
This is out of scope of this group.But I require the clarification pretty urgently.
My Oracle database is parallely enabled.
Still,in a particular table queries do not work "parallely" always.
How is this? (9 Replies)
Discussion started by: kthri
9 Replies
7. UNIX for Dummies Questions & Answers
Hi to all,
I'm interested in finding an introduction about Performance Tuning under Unix (or Linux); can somebody please point me in the right direction?
Best regards (1 Reply)
Discussion started by: domyalex
1 Replies
8. Filesystems, Disks and Memory
Hi all,
long time ago I posted something, but now, it is needed again :(
Currently, I am handling with a big NFS Server for more than 200 clients, this sever has to work with 256 NFSDs. Because of this huge amount of NFSDs, there are thousands of small write accesses down to the disk and... (3 Replies)
Discussion started by: malcom
3 Replies
9. UNIX for Dummies Questions & Answers
can someone tell me a good site to go to in order to learn this. please do not recommen nay books because i dont have interest in that. if you know of any good sites with good straight forward explanation on how to split loads on machines that has excessive loading, please let me know
Also,... (1 Reply)
Discussion started by: TRUEST
1 Replies
MADVISE(2) BSD System Calls Manual MADVISE(2)
NAME
madvise, posix_madvise -- give advice about use of memory
SYNOPSIS
#include <sys/mman.h>
int
madvise(void *addr, size_t len, int advice);
int
posix_madvise(void *addr, size_t len, int advice);
DESCRIPTION
The madvise() system call allows a process that has knowledge of its memory behavior to describe it to the system. The advice passed in may
be used by the system to alter its virtual memory paging strategy. This advice may improve application and system performance. The behavior
specified in advice can only be one of the following values:
MADV_NORMAL Indicates that the application has no advice to give on its behavior in the specified address range. This is the system
default behavior. This is used with madvise() system call.
POSIX_MADV_NORMAL
Same as MADV_NORMAL but used with posix_madvise() system call.
MADV_SEQUENTIAL Indicates that the application expects to access this address range in a sequential manner. This is used with madvise()
system call.
POSIX_MADV_SEQUENTIAL
Same as MADV_SEQUENTIAL but used with posix_madvise() system call.
MADV_RANDOM Indicates that the application expects to access this address range in a random manner. This is used with madvise() system
call.
POSIX_MADV_RANDOM
Same as MADV_RANDOM but used with posix_madvise() system call.
MADV_WILLNEED Indicates that the application expects to access this address range soon. This is used with madvise() system call.
POSIX_MADV_WILLNEED
Same as MADV_WILLNEED but used with posix_madvise() system call.
MADV_DONTNEED Indicates that the application is not expecting to access this address range soon. This is used with madvise() system call.
POSIX_MADV_DONTNEED
Same as MADV_DONTNEED but used with posix_madvise() system call.
MADV_FREE Indicates that the application will not need the information contained in this address range, so the pages may be reused
right away. The address range will remain valid. This is used with madvise() system call.
MADV_ZERO_WIRED_PAGES
Indicates that the application would like the wired pages in this address range to be zeroed out if the address range is
deallocated without first unwiring the pages (i.e. a munmap(2) without a preceding munlock(2) or the application quits).
This is used with madvise() system call.
The posix_madvise() behaves same as madvise() except that it uses values with POSIX_ prefix for the advice system call argument.
RETURN VALUES
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error.
ERRORS
madvise() fails if one or more of the following are true:
[EINVAL] The value of advice is incorrect.
[EINVAL] The address range includes unallocated regions.
[ENOMEM] The virtual address range specified by the addr and len are outside the range allowed for the address space.
LEGACY SYNOPSIS
#include <sys/types.h>
#include <sys/mman.h>
int
madvise(caddr_t addr, size_t len, int advice);
int
posix_madvise(caddr_t addr, size_t len, int advice);
The include file <sys/types.h> is necessary. The type of addr has changed.
SEE ALSO
mincore(2), minherit(2), mprotect(2), msync(2), munmap(2), compat(5)
HISTORY
The madvise function first appeared in 4.4BSD. The posix_madvise function is part of IEEE 1003.1-2001 and was first implemented in Mac OS X
10.2.
BSD
June 9, 1993 BSD