Sponsored Content
Full Discussion: CIO/DIO and JFS2 read ahead
Operating Systems AIX CIO/DIO and JFS2 read ahead Post 302257412 by hariza on Wednesday 12th of November 2008 05:20:46 AM
Old 11-12-2008
CIO/DIO and JFS2 read ahead

Hi Guys,

I wonder if after enabling CIO/DIO at the filesystem level and assuming that CIO/DIO will bypass the JFS2 read ahead available when not using CIO/DIO my questionis what parameters I can play with to tune/improve the CIO in order to obtain similar performance for sequential reads ( backups or big scans). I believe that while using file system caching/buffering read ahead plays a huge performance role. So any advise on how/what parameters I should consider modify in order to improve the CIO/DIO performance for large sequential reads.

Thanks in Advance.

Harby.
 

8 More Discussions You Might Find Interesting

1. HP-UX

Read-ahead in HP-UX

One cool thing about unix is that it predicts disk blocks that you may need and tries to have them in core before you need them. Over the years, various unix vendors tried various algorithms to improve performance. HP has patented their latest algorithm... Multi-threaded Read Ahead Prediction... (0 Replies)
Discussion started by: Perderabo
0 Replies

2. AIX

JFS and JFS2

hi all, can sumbody give me a link which gives the basic layout of JFS, JFS2 and the veritas file system. and i also want to know about the data structures used in this filsystem thanx in advance (0 Replies)
Discussion started by: anwerreyaz
0 Replies

3. Shell Programming and Scripting

PERL look ahead and behind ...

I would like to search a router config file for "ip address $ip", once found, I want to grab the line just before that contains "interface $interfacetype" basically saying, 10.3.127.9 is assigned to "Loopback1" given the below as an example. interface Loopback1 ip address 10.3.127.9... (1 Reply)
Discussion started by: popeye
1 Replies

4. AIX

Jfs and jfs2

Hi all, Can anyone define the difference between jfs and jfs2 filesystem as well as usage of jfs log files.... Thanks.... (7 Replies)
Discussion started by: sumathi.k
7 Replies

5. Red Hat

How to enable AIO and DIO on rhel5 64bit?

Hi Friends, Please help me to understand, how to enable async disk IO and Direct disk IO in ext3 filesystem on rhel5. Regards, Arumon (0 Replies)
Discussion started by: arumon
0 Replies

6. AIX

Slow NFS when cio/dio enabled

Hi, I have a bit of a NFS problem on AiX 6.1 : When I set the mount to cio and dio - needed for a database app - Everything slows down. The following is copying 700mb, top one is a normal mount bottom one is a mount with the cio/dio option enabled : # ./a.sh Wed Jan 11 11:41:24 GMT 2012... (5 Replies)
Discussion started by: AJCG1976
5 Replies

7. AIX

AIX JFS2 content

Hello! I have a LPAR with 51GB RAM topas shows 21% of memory for client pages (~11Gb) svmon -G show 2906772 client pages in use (~11Gb) but then i try to investigate per process client memory usage svmon -P -O filtertype=client and summarize inuse column, i get only 347880 pages... (1 Reply)
Discussion started by: sys
1 Replies

8. UNIX for Beginners Questions & Answers

Two days ahead

Hi, I have a code that will show one day ahead, how to make it show two days ahead p-dev1-db-tst:/$ day=$(TZ=IST-24 date +%d) p-dev1-db-tst:/$ echo $day 17 p-dev1-db-tst:/$ Regards, Adam (5 Replies)
Discussion started by: answer
5 Replies
POSIX_MADVISE(3)					     Linux Programmer's Manual						  POSIX_MADVISE(3)

NAME
posix_madvise - give advice about patterns of memory usage SYNOPSIS
#include <sys/mman.h> int posix_madvise(void *addr, size_t len, int advice); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): posix_madvise(): _POSIX_C_SOURCE >= 200112L DESCRIPTION
The posix_madvise() function allows an application to advise the system about its expected patterns of usage of memory in the address range starting at addr and continuing for len bytes. The system is free to use this advice in order to improve the performance of memory accesses (or to ignore the advice altogether), but calling posix_madvise() shall not affect the semantics of access to memory in the speci- fied range. The advice argument is one of the following: POSIX_MADV_NORMAL The application has no special advice regarding its memory usage patterns for the specified address range. This is the default behavior. POSIX_MADV_SEQUENTIAL The application expects to access the specified address range sequentially, running from lower addresses to higher addresses. Hence, pages in this region can be aggressively read ahead, and may be freed soon after they are accessed. POSIX_MADV_RANDOM The application expects to access the specified address range randomly. Thus, read ahead may be less useful than normally. POSIX_MADV_WILLNEED The application expects to access the specified address range in the near future. Thus, read ahead may be beneficial. POSIX_MADV_DONTNEED The application expects that it will not access the specified address range in the near future. RETURN VALUE
On success, posix_madvise() returns 0. On failure, it returns a positive error number. ERRORS
EINVAL addr is not a multiple of the system page size or len is negative. EINVAL advice is invalid. ENOMEM Addresses in the specified range are partially or completely outside the caller's address space. VERSIONS
Support for posix_madvise() first appeared in glibc version 2.2. CONFORMING TO
POSIX.1-2001. NOTES
POSIX.1 permits an implementation to generate an error if len is 0. On Linux, specifying len as 0 is permitted (as a successful no-op). In glibc, this function is implemented using madvise(2). However, since glibc 2.6, POSIX_MADV_DONTNEED is treated as a no-op, because the corresponding madvise(2) value, MADV_DONTNEED, has destructive semantics. SEE ALSO
madvise(2), posix_fadvise(2) 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 POSIX_MADVISE(3)
All times are GMT -4. The time now is 08:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy