Sponsored Content
Full Discussion: CIO/DIO and JFS2 read ahead
Operating Systems AIX CIO/DIO and JFS2 read ahead Post 302258238 by hariza on Friday 14th of November 2008 05:31:35 AM
Old 11-14-2008
Furthermore to this topic so basically for a Warehouse Database server with databases bigger than 500 Gigs and where a lot of large sequential reads are necessary CIO won't add any benefit to it in terms of performance?.
 

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
TM::Bulk(3pm)						User Contributed Perl Documentation					     TM::Bulk(3pm)

NAME
TM::Bulk - Topic Maps, Bulk Retrieval Trait SYNOPSIS
my $tm = ..... # get a map from anywhere use TM::Bulk; use Class::Trait; Class::Trait->apply ($tm, 'TM::Bulk'); # give the map the trait # find out environment of topic my $vortex = $tm->vortex ('some-lid', { 'types' => [ 'types' ], 'instances' => [ 'instances*', 0, 20 ], 'topic' => [ 'topic' ], 'roles' => [ 'roles', 0, 10 ], 'members' => [ 'players' ], }, ); # find names of topics (optionally using a scope preference list) my $names = $tm->names ([ 'ccc', 'bbb', 'aaa' ], [ 's1', 's3', '*' ]); DESCRIPTION
Especially when you build user interfaces, you might need access to a lot of topic-related information. Instead of collecting this 'by foot' the following methods help you achieve this more effectively. names $name_hash_ref = $tm->names ($lid_list_ref, [ $scope_list_ref ] ) This method takes a list (reference) of topic ids and an optional list of scoping topic ids. For the former it will try to find the names (topic names for TMDM acolytes). If the list of scopes is empty then the preference is on the unconstrained scope. If no name for a topic is in that scope, some other will be used. If the list of scopes is non-empty, it directs to look first for a name in the first scoping topic, then second, and so on. If you want to have one name in any case, append "*" to the scoping list. If no name exist for a particular lid, then an "undef" is returned in the result hash. References to non-existing topics are ignored. The overall result is a hash (reference). The keys are of the form "topic-id @ scope-id" (without the blanks) and the name strings are the values. vortex $info = $tm->vortex (, $vortex_lid, $what_hashref, $scope_list_ref ) This method returns a lot of information about a particular toplet (vortex). The function expects the following parameters: lid: the lid of the toplet in question what: a hash reference describing the extent of the information (see below) scopes: a list (reference) to scopes (currently NOT honored) To control what exactly should be returned, the "what" hash reference can contain following components. All of them being tagged with <n,m> accept an additional pair of integer specify the range which should be returned. To ask for the first twenty, use "0,19", for the next "20,39". The order in which the identifiers is returned is undefined but stable over subsequent read-only calls. topic: fetches the toplet (which is only the subject locator, subject indicators information). names (<n,m>): fetches all names (as array reference triple [ type, scope, string value ]) occurrences (<n,m>): fetches all occurrences (as array reference triple [ type, scope, value ]) instances (<n,m>): fetches all toplets which are direct instances of the vortex (that is regarded as class here); instances* (<n,m>): same as "instances", but including all instances of subclasses of the vortex types (<n,m>): fetches all (direct) types of the vortex (that is regarded as instance here) types* (<n,m>): fetches all (direct and indirect) types of the vortex (that is regarded as instance here) subclasses (<n,m>): fetches all direct subclasses subclasses* (<n,m>): same as "subclasses", but creates reflexive, transitive closure superclasses (<n,m>): fetches all direct superclasses superclasses* (<n,m>): same as "superclasses", but creates reflexive, transitive closure roles (<n,m>): fetches all assertion ids where the vortex plays a role peers (<n,m>): fetches all topics which are also a direct instance of any of the (direct) types of this topic peers* (<n,m>): fetches all topics which are also a (direct or indirect) instances of any of the (direct) types of this topic peers** (<n,m>): fetches all topics which are also a (direct or indirect) instances of any of the (direct or indirect) types of this topic The function will determine all of the requested information and will prepare a hash reference storing each information into a hash component. Under which name this information is stored, the caller can determine with the hash above as the example shows: Example: $vortex = $tm->vortex ('some-lid', { 'types' => [ 'types' ], 'instances' => [ 'instances*', 0, 20 ], 'topic' => [ 'topic' ], 'roles' => [ 'roles', 0, 10 ], }, ); The method dies if "lid" does not identify a proper toplet. SEE ALSO
TM::Overview COPYRIGHT AND LICENSE
Copyright 200[3-57] by Robert Barta, <drrho@cpan.org> This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.10.1 2008-04-23 TM::Bulk(3pm)
All times are GMT -4. The time now is 09:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy