AIX Performance Tuning Part 1

Jaqui Lynch
AIX Performance Tuning Part 1
lynchj@forsythe.com
 Agenda

• Part 1 • Part 2
• CPU • I/O
• Memory tuning • Volume Groups and File
• Network systems
• Starter Set of Tunables • AIO and CIO for Oracle
• Performance Tools

2
 CPU

3
 Applications and SPLPARs
• Applications do not need to be aware of Micro-Partitioning
• Not all applications benefit from SPLPARs
• Applications that may not benefit from Micro-Partitioning:
• Applications with a strong response time requirements for transactions may find Micro-Partitioning
detrimental:
• Because virtual processors can be dispatched at various times during a timeslice
• May result in longer response time with too many virtual processors:
• Each virtual processor with a small entitled capacity is in effect a slower CPU
• Compensate with more entitled capacity (2-5% PUs over plan)
• Applications with polling behavior
• CPU intensive application examples: DSS, HPC, SAS
• Applications that are good candidates for Micro-Partitioning:
• Ones with low average CPU utilization, with high peaks:
• Examples: OLTP, web applications, mail server, directory servers

• In general Oracle databases are fine in the shared processor pool

• For licensing reasons you may want to use a separate pool for databases

4
 Logical Processors
Logical Processors represent SMT threads

LPAR 1 LPAR 2 LPAR 1 LPAR 1

SMT on SMT off SMT on SMT off

vmstat - Icpu=4 lcpu=2 Icpu=4 Icpu=2

L L L L L L L L Logical
V V V V V=0.6 V=0.6 V=0.4
V=0.4 Virtual
2 Cores 2 Cores
Dedicated Dedicated PU=1.2 PU=0.8
VPs under the covers VPs under the covers
Weight=128 Weight=192
Hypervisor
Core Core Core Physical
Core Core Core Core
Core Core Core

5
 Dispatching in shared pool

• VP gets dispatched to a core

• First time this becomes the home node
• All 4 threads for the VP go with the VP
• VP runs to the end of its entitlement
• If it has more work to do and noone else wants the core it gets more
• If it has more work to do but other VPs want the core then it gets
context switched and put on the home node runQ
• If it can’t get serviced in a timely manner it goes to the global runQ
and ends up running somewhere else but its data may still be in the
memory on the home node core

6
 POWER6 vs POWER7 Virtual Processor Unfolding

Virtual Processor is activated at different utilization threshold for P5/P6 and P7

P5/P6 loads the 1st and 2nd SMT threads to about 80% utilization and then unfolds a VP

P7 loads first thread on the VP to about 50% then unfolds a VP

Once all VPs unfolded then 2nd SMT threads are used

Once 2nd threads are loaded then tertiaries are used

This is called raw throughput mode
Why?
Raw Throughput provides the highest per-thread throughput and best response times at the expense of
activating more physical cores

Both systems report same physical consumption

This is why some people see more cores being used in P7 than in P6/P5, especially if they did not reduce
VPs when they moved the workload across.

HOWEVER, idle time will most likely be higher

I call P5/P6 method “stack and spread” and P7 “spread and stack”
7
 Scaled Throughput
• P7 and P7+ with AIX v6.1 TL08 and AIX v7.1 TL02
• Dispatches more SMT threads to a VP core before unfolding additional VPs
• Tries to make it behave a bit more like P6

• Raw provides the highest per-thread throughput

and best response times at the expense of activating more physical core

• Scaled provides the highest core throughput at the expense of per-thread response times and throughput.
It also provides the highest system-wide throughput per VP because tertiary thread capacity is “not left on the
table.”

• schedo –p –o vpm_throughput_mode=
0 Legacy Raw mode (default)
1 “Enhanced Raw” mode with a higher threshold than legacy
2 Scaled mode, use primary and secondary SMT threads
4 Scaled mode, use all four SMT threads
Dynamic Tunable

• SMT unfriendly workloads could see an enormous per thread performance degradation

8
 Understand SMT
• SMT
• Threads dispatch via a Virtual Processor (VP)
• Overall more work gets done (throughput)
• Individual threads run a little slower SMT Thread
• SMT1: Largest unit of execution work Primary 0
• SMT2: Smaller unit of work, but provides greater
amount of execution work per cycle 1
Secondary
• SMT4: Smallest unit of work, but provides the
maximum amount of execution work per cycle
Tertiary 2 3
• On POWER7, a single thread cannot exceed 65%
utilization
• On POWER6 or POWER5, a single thread can Diagram courtesy of IBM

consume 100%
• Understand thread dispatch order

• VPs are unfolded when threshold is reached

• P5 and P6 primary and secondary threads are loaded to 80% before another
VP unfolded
• In P7 primary threads are loaded to 50%, unfolds VPs, then secondary
threads used. When they are loaded to 50% tertiary threads are dispatched
9
 POWER6 vs POWER7 SMT Utilization
POWER6 SMT2 POWER7 SMT2 POWER7 SMT4
Htc0 busy 100% Htc0 busy ~70% Htc0 busy ~63% ~75%
Htc1 idle busy Htc1 idle busy Htc1 idle busy
Htc2 idle ~87%
Htc3 idle
Up to 100%
Htc0 busy
100% Htc0 busy 100%
Htc1 busy busy Htc1 busy busy
“busy” = user% + system%

POWER7 SMT=2 70% & SMT=4 63% tries to show potential spare capacity
• Escaped most peoples attention
• VM goes 100% busy at entitlement & 100% from there on up to 10 x more CPU
SMT4 100% busy 1st CPU now reported as 63% busy
• 2nd, 3rd and 4th LCPUs each report 12% idle time which is approximate

Nigel Griffiths Power7 Affinity – Session 19 and 20 - http://tinyurl.com/newUK-PowerVM-VUG

10
 More on Dispatching
How dispatching works
Example - 1 core with 6 VMs assigned to it

VPs for the VMs on the core get dispatched (consecutively) and their threads run
As each VM runs the cache is cleared for the new VM
When entitlement reached or run out of work CPU is yielded to the next VM
Once all VMs are done then system determines if there is time left
Assume our 6 VMs take 6MS so 4MS is left
Remaining time is assigned to still running VMs according to weights
VMs run again and so on

Problem - if entitlement too low then dispatch window for the VM casn be too low
If VM runs multiple times in a 10ms window then it does not run full speed as cache has to be warmed up
If entitlement higher then dispatch window is longer and cache stays warm longer - fewer cache misses

Nigel Griffiths Power7 Affinity – Session 19 and 20 - http://tinyurl.com/newUK-PowerVM-VUG

11
 Entitlement and VPs
• Utilization calculation for CPU is different between POWER5, 6 and POWER7
• VPs are also unfolded sooner (at lower utilization levels than on P6 and P5)

• This means that in POWER7 you need to pay more attention to VPs
• You may see more cores activated a lower utilization levels
• But you will see higher idle
• If only primary SMT threads in use then you have excess VPs

• Try to avoid this issue by:

• Reducing VP counts
• Use realistic entitlement to VP ratios
• 10x or 20x is not a good idea
• Try setting entitlement to .6 or .7 of VPs
• Ensure workloads never run consistently above 100% entitlement
• Too little entitlement means too many VPs will be contending for the cores

• Performance may (in most cases, will) degrade when the number of Virtual Processors in an
LPAR exceeds the number of physical processors

12
 Useful processor Commands

• lsdev –Cc processor

• lsattr –EL proc0
• bindprocessor –q
• sar –P ALL or sar –mu –P ALL
• topas, nmon
• lparstat
• vmstat (use –IW or -v)
• iostat
• mpstat –s
• lssrad -av

13
 lparstat 30 2
lparstat 30 2 output

System configuration: type=Shared mode=Uncapped smt=4 lcpu=72 mem=319488MB psize=17 ent=12.00

%user %sys %wait %idle physc %entc lbusy app vcsw phint
46.8 11.6 0.5 41.1 11.01 91.8 16.3 4.80 28646 738
48.8 10.8 0.4 40.0 11.08 92.3 16.9 4.88 26484 763

psize = processors in shared pool

lbusy = %occupation of the LCPUs at the system and user level
app = Available physical processors in the pool
vcsw = Virtual context switches (virtual processor preemptions)
phint = phantom interrupts received by the LPAR
interrupts targeted to another partition that shares the same physical processor
i.e. LPAR does an I/O so cedes the core, when I/O completes the interrupt is sent to the
core but different LPAR running so it says “not for me”

NOTE – Must set “Allow performance information collection” on the LPARs to see good values for app, etc
Required for shared pool monitoring
14
 Using sar –mu -P ALL (Power7 & SMT4)
AIX (ent=10 and 16 VPs) so per VP physc entitled is about .63

System configuration: lcpu=64 ent=10.00 mode=Uncapped

14:24:31 cpu %usr %sys %wio %idle physc %entc
Average 0 77 22 0 1 0.52 5.2
1 37 14 1 48 0.18 1.8
2 0 1 0 99 0.10 1.0
3 0 1 0 99 0.10 1.0 .9 physc

4 84 14 0 1 0.49 4.9
5 42 7 1 50 0.17 1.7
6 0 1 0 99 0.10 1.0
7 0 1 0 99 0.10 1.0 .86 physc

8 88 11 0 1 0.51 5.1
9 40 11 1 48 0.18 1.8
............. Lines for 10-62 were here
63 0 1 0 99 0.11 1.1
- 55 11 0 33 12.71 127.1

So we see we are using 12.71 cores which is 127.1% of our entitlement

This is the sum of all the physc lines – cpu0-3 = proc0 = VP0

May see a U line if in SPP and is unused LPAR capacity (compared against entitlement)
15
 mpstat -s
mpstat –s 1 1
System configuration: lcpu=64 ent=10.0 mode=Uncapped

Proc0 Proc4 Proc8

89.06% 84.01% 81.42%
cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 cpu8 cpu9 cpu10 cpu11
41.51% 31.69% 7.93% 7.93% 42.41% 24.97% 8.31% 8.32% 39.47% 25.97% 7.99% 7.99%

Proc12 Proc16 Proc20

82.30% 38.16% 86.04%
cpu12 cpu13 cpu14 cpu15 cpu16 cpu17 cpu18 cpu19 cpu20 cpu21 cpu22 cpu23
43.34% 22.75% 8.11% 8.11% 23.30% 4.97% 4.95% 4.94% 42.01% 27.66% 8.18% 8.19%

………………………………

Proc60
99.11%
cpu60 cpu61 cpu62 cpu63
62.63% 13.22% 11.63% 11.63%

Proc* are the virtual CPUs

CPU* are the logical CPUs (SMT threads)

16
 nmon Summary

17
 lparstat – bbbl tab in nmon
lparno 3
lparname gandalf
CPU in sys 24
Virtual CPU 16
Logical CPU 64
smt threads 4
capped 0
min Virtual 8
max Virtual 20 Compare VPs to poolsize
min Logical 8 LPAR should not have more
max Logical 80
min Capacity 8 VPs than the poolsize
max Capacity 16

Entitled Capacity 10
min Memory MB 131072

max Memory MB 327680

online Memory 303104
Pool CPU 16
Weight 150
pool id 2

18
Entitlement and vps from lpar tab in nmon

19
Cpu by thread from cpu_summ tab in nmon

20
 vmstat -IW
bnim: vmstat -IW 2 2

vmstat –IW 60 2

System configuration: lcpu=12 mem=24832MB ent=2.00

kthr memory page faults cpu
----------- ----------- ------------------------ ------------ -----------------------
r b p w avm fre fi fo pi po fr sr in sy cs us sy id wa pc ec
3 1 0 2 2708633 2554878 0 46 0 0 0 0 3920 143515 10131 26 44 30 0 2.24 112.2
6 1 0 4 2831669 2414985 348 28 0 0 0 0 2983 188837 8316 38 39 22 0 2.42 120.9

Note pc=2.42 is 120.0% of entitlement

-I shows I/O oriented view and adds in the p column

p column is number of threads waiting for I/O messages to raw devices.

-W adds the w column (only valid with –I as well)

w column is the number of threads waiting for filesystem direct I/O (DIO) and concurrent I/O (CIO)

r column is average number of runnable threads (ready but waiting to run + those running)
This is the global run queue – use mpstat and look at the rq field to get the run queue for each logical CPU

b column is average number of threads placed in the VMM wait queue (awaiting resources or I/O)

21
 vmstat –IW
lcpu 72 Mem 319488MB Ent 12

r b p w avm fre fi fo pi po fr sr in sy cs us sy id wa pc ec
17 0 0 2 65781580 2081314 2 5 0 0 0 0 11231 146029 22172 52 13 36 0 11.91 99.2
11 0 0 5 65774009 2088879 2 136 0 0 0 0 11203 126677 20428 47 13 40 0 11.29 94.1
14 0 0 4 65780238 2082649 2 88 0 0 0 0 11463 220780 22024 50 14 36 0 12.62 105.2
20 0 0 9 65802196 2060643 51 114 0 0 0 0 9434 243080 21883 55 15 29 1 12.98 108.2
26 1 0 7 65810733 2052105 9 162 0 0 0 0 9283 293158 22779 60 16 23 1 13.18 109.8
18 1 0 5 65814822 2048011 0 0 0 0 0 0 11506 155344 27308 53 13 33 0 13.51 112.6
18 0 0 5 65798165 2064666 0 0 0 0 0 0 10868 200123 25143 53 14 32 0 13.27 110.6
17 0 0 5 65810136 2052662 4 0 0 0 0 0 12394 230802 29167 51 17 32 1 14.14 117.8
15 0 0 7 65796659 2066142 0 0 0 0 0 0 12301 217839 27142 48 16 35 0 13.42 111.9
13 0 0 8 65798332 2064469 1 20 0 0 0 0 14001 160576 30871 44 16 39 0 11.41 95.1
15 1 0 4 65795292 2067486 7 212 0 0 0 0 14263 215226 31856 51 14 35 0 13.33 111.1
19 0 0 7 65807317 2055454 0 0 0 0 0 0 11887 306416 26162 52 13 34 0 13.85 115.4
13 0 0 5 65807079 2055689 0 0 0 0 0 0 11459 196036 26782 49 14 36 0 12.49 104.1
19 0 0 5 65810475 2052293 0 0 0 0 0 0 13187 292694 28050 52 13 35 0 14 116.7
17 0 0 11 65819751 2043008 4 0 0 0 0 0 12218 225829 27516 51 14 35 0 13.14 109.5
26 0 0 10 65825374 2037373 1 35 0 0 0 0 11447 220479 23273 55 13 32 0 13.91 115.9
26 0 0 6 65820723 2042005 6 182 0 0 0 0 11652 331234 26888 63 11 25 1 14.3 119.2
18 1 0 6 65816444 2046275 4 0 0 0 0 0 11628 184413 25634 51 14 35 0 13.19 110
20 0 0 8 65820880 2041819 0 13 0 0 0 0 12332 190716 28370 51 14 36 0 13.37 111.4
17 0 0 6 65822872 2039836 0 0 0 0 0 0 13269 128353 30880 47 14 39 0 11.46 95.5
15 0 0 5 65832214 2030493 0 0 0 0 0 0 12079 207403 26319 51 13 35 0 13.24 110.4
14 0 0 8 65827065 2035639 17 14 0 0 0 0 14060 117935 32407 48 15 36 0 12.06 100.5
15 0 0 4 65824658 2037996 10 212 0 0 0 0 12690 137533 27678 44 20 36 0 13.53 112.8
18 0 0 10 65817327 2045339 0 0 0 0 0 0 12665 161261 28010 50 14 36 0 12.69 105.8
17 0 0 8 65820348 2042321 0 0 0 0 0 0 14047 228897 28475 53 13 34 0 14.44 120.4
16 0 0 6 65817053 2045609 0 0 0 0 0 0 12953 160629 26652 50 14 35 0 12.83 106.9
18 0 0 12 65813683 2048949 0 0 0 0 0 0 11766 198577 26593 53 13 33 0 13.54 112.9
18 0 0 13 65808798 2053853 18 23 0 0 0 0 12195 209122 27152 53 14 33 0 13.86 115.5
12 1 0 14 65800471 2062164 6 218 0 0 0 0 12429 182117 27787 55 13 31 1 13.38 111.5
18 2 0 8 65805624 2056998 6 72 0 0 0 0 12134 209260 25250 54 13 32 0 13.73 114.4

r b p w avm fre fi fo pi po fr sr in sy cs us sy id wa pc ec

Average 17.33 0.23 0.00 7.10 65809344 2053404 5.00 50 0.00 0.00 0.00 0.00 12134.80 203285 26688 51.53 14.10 33.93 0.17 13.14 109.48
Max 26.00 2.00 0.00 14.00 65832214 2088879 51.00 218 0.00 0.00 0.00 0.00 14263.00 331234 32407 63.00 20.00 40.00 1.00 14.44 120.40
Min 11.00 0.00 0.00 2.00 65774009 2030493 0.00 0 0.00 0.00 0.00 0.00 9283.00 117935 20428 44.00 11.00 23.00 0.00 11.29 94.10

22
 MEMORY

23
 Memory Types
• Persistent
• Backed by filesystems
• Working storage
• Dynamic
• Includes executables and their work areas
• Backed by page space
• Shows as avm in a vmstat –I (multiply by 4096 to get bytes instead of pages) or as
%comp in nmon analyser or as a percentage of memory used for computational pages in
vmstat –v
• ALSO NOTE – if %comp is near or >97% then you will be paging and need more memory
• Prefer to steal from persistent as it is cheap
• minperm, maxperm, maxclient, lru_file_repage and page_steal_method all
impact these decisions

24
 Correcting Paging
From vmstat -v
11173706 paging space I/Os blocked with no psbuf

lsps output on above system that was paging before changes were made to tunables
lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging01 hdisk3 pagingvg 16384MB 25 yes yes lv
paging00 hdisk2 pagingvg 16384MB 25 yes yes lv
hd6 hdisk0 rootvg 16384MB 25 yes yes lv

lsps -s
Total Paging Space Percent Used Can also use vmstat –I and vmstat -s
49152MB 1%

Should be balanced – NOTE VIO Server comes with 2 different sized page datasets on one hdisk (at least until FP24)

Best Practice
More than one page volume
All the same size including hd6
Page spaces must be on different disks to each other
Do not put on hot disks
Mirror all page spaces that are on internal or non-raided disk
If you can’t make hd6 as big as the others then swap it off after boot

All real paging is bad

25
 Memory with lru_file_repage=0
lru_file_repage=0
• minperm=3
• Always try to steal from filesystems if filesystems are using more than 3% of memory
• maxperm=90
• Soft cap on the amount of memory that filesystems or network can use
• Superset so includes things covered in maxclient as well
• maxclient=90
• Hard cap on amount of memory that JFS2 or NFS can use – SUBSET of maxperm

• lru_file_repage goes away in v7 later TLs

• It is still there but you can no longer change it

All AIX systems post AIX v5.3 (tl04 I think) should have these 3 set
On v6.1 and v7 they are set by default

26
 page_steal_method
• Default in 5.3 is 0, in 6 and 7 it is 1
• What does 1 mean?
• lru_file_repage=0 tells LRUD to try and steal from filesystems
• Memory split across mempools
• LRUD manages a mempool and scans to free pages
• 0 – scan all pages
• 1 – scan only filesystem pages

27
 page_steal_method Example
• 500GB memory
• 50% used by file systems (250GB)
• 50% used by working storage (250GB)
• mempools = 5
• So we have at least 5 LRUDs each controlling about 100GB memory
• Set to 0
• Scans all 100GB of memory in each pool
• Set to 1
• Scans only the 50GB in each pool used by filesystems
• Reduces cpu used by scanning
• When combined with CIO this can make a significant difference

28
 Looking for Problems
• lssrad –av
• mpstat –d
• topas –M
• svmon
• Try –G –O unit=auto,timestamp=on,pgsz=on,affinity=detail
options
• Look at Domain affinity section of the report
• Etc etc

29
 Memory Problems
• Look at computational memory use
• Shows as avm in a vmstat –I (multiply by 4096 to get bytes instead of pages)
• or as %comp in nmon analyser
• or as a percentage of memory used for computational pages in vmstat –v

• NOTE – if %comp is near or >97% then you will be paging and need more memory
• Try svmon –P –Osortseg=pgsp –Ounit=MB | more
• This shows processes using the most pagespace in MB
• You can also try the following:
• svmon –P –Ofiltercat=exclusive –Ofiltertype=working –Ounit=MB| more

30
 nmon memnew tab

31
 nmon memuse tab

32
 Memory Tips

Avoid having chips without DIMMs.

Attempt to fill every chip’s DIMM slots, activating as needed.
Hypervisor tends to avoid activating cores without “local” memory.

DIMMs

Empty
DIMMs

DIMMs
Cores Cores Cores Cores
DIMMs

Empty
DIMMs

DIMMs
Cores Cores Cores Cores
Empty
DIMMs

DIMMs
Empty
Cores Cores Cores Cores
DIMMs

DIMMs
Empty

DIMMs
Cores Cores Cores Cores

Diagram courtesy of IBM

33
lssrad -av
Small LPAR on 770
REF1 SRAD MEM CPU REF1 where
REF1=0 SRAD=0 is local
0 REF1=0 SRAD=1 is near
0 88859.50 0-7 Other REF values are far
This is relative to the process home
2 36354.00 SRAD = CPU + Memory group
1 MEM = Mbytes
CPU = LCPU number, assuming SMT4
1 42330.00 8-11
3 20418.00

Large LPAR on 770 – note REF=1 SRAD 3

REF1 SRAD MEM CPU
0
0 247956.00 0-47 52-55 60-63
2 10458.00 68-71
1
1 49035.50 48-51 56-59 64-67
3 2739.0

34
 Starter set of tunables 1
For AIX v5.3
No need to set memory_affinity=0 after 5.3 tl05

MEMORY
vmo -p -o minperm%=3
vmo -p -o maxperm%=90
vmo -p -o maxclient%=90
vmo -p -o minfree=960 We will calculate these
vmo -p -o maxfree=1088 We will calculate these
vmo -p -o lru_file_repage=0
vmo -p -o lru_poll_interval=10
vmo -p -o page_steal_method=1

For AIX v6 or v7
Memory defaults are already correctly except minfree and maxfree
If you upgrade from a previous version of AIX using migration then you need to check the settings
after

35
 Starter set of tunables 2
The parameters below should be reviewed and changed
(see vmstat –v and lvmo –a later)

PBUFS
Use the new way (coming up)

JFS2
ioo -p -o j2_maxPageReadAhead=128
(default above may need to be changed for sequential) – dynamic
Difference between minfree and maxfree should be > that this value
j2_dynamicBufferPreallocation=16
Max is 256. 16 means 16 x 16k slabs or 256k
Default that may need tuning but is dynamic
Replaces tuning j2_nBufferPerPagerDevice until at max.

Network changes in later slide

36
 vmstat –v Output

3.0 minperm percentage

90.0 maxperm percentage
45.1 numperm percentage
45.1 numclient percentage
90.0 maxclient percentage

1468217 pending disk I/Os blocked with no pbuf pbufs

11173706 paging space I/Os blocked with no psbuf pagespace
2048 file system I/Os blocked with no fsbuf JFS
238 client file system I/Os blocked with no fsbuf NFS/VxFS
39943187 external pager file system I/Os blocked with no fsbuf JFS2

numclient=numperm so most likely the I/O being done is JFS2 or NFS or VxFS
Based on the blocked I/Os it is clearly a system using JFS2
It is also having paging problems
pbufs also need reviewing

37
 vmstat –v Output
uptime
02:03PM up 39 days, 3:06, 2 users, load average: 17.02, 15.35, 14.27

9 memory pools
3.0 minperm percentage
90.0 maxperm percentage
14.9 numperm percentage
14.9 numclient percentage
90.0 maxclient percentage

66 pending disk I/Os blocked with no pbuf pbufs

0 paging space I/Os blocked with no psbuf pagespace
1972 filesystem I/Os blocked with no fsbuf JFS
527 client filesystem I/Os blocked with no fsbuf NFS/VxFS
613 external pager filesystem I/Os blocked with no fsbuf JFS2
numclient=numperm so most likely the I/O being done is JFS2 or NFS or VxFS
Based on the blocked I/Os it is clearly a system using JFS2
This is a fairly healthy system as it has been up 39 days with few blockages

38
 Memory Pools and fre column
• fre column in vmstat is a count of all the free pages across all the memory pools
• When you look at fre you need to divide by memory pools
• Then compare it to maxfree and minfree
• This will help you determine if you are happy, page stealing or thrashing
• You can see high values in fre but still be paging
• In below if maxfree=2000 and we have 10 memory pools then we only have 990 pages free in
each pool on average. With minfree=960 we are page stealing and close to thrashing.

kthr memory page faults cpu

-------- - ---------- ------------------------ ------------ -----------
r b p avm fre fi fo pi po fr sr in sy cs us sy id wa
70 309 0 8552080 9902 75497 9615 9 3 84455 239632 18455 280135 91317 42 37 0 20

Assuming 10 memory pools (you get this from vmstat –v)

9902/10 = 990.2 so we have 990 pages free per memory pool
If maxfree is 2000 and minfree is 960 then we are page stealing and very close to thrashing

39
 Calculating minfree and maxfree
vmstat –v | grep memory
3 memory pools

vmo -a | grep free

maxfree = 1088
minfree = 960

Calculation is:
minfree = (max (960,(120 * lcpus) / memory pools))
maxfree = minfree + (Max(maxpgahead,j2_maxPageReadahead) * lcpus) / memory pools

So if I have the following:

Memory pools = 3 (from vmo –a or kdb)
J2_maxPageReadahead = 128
CPUS = 6 and SMT on so lcpu = 12
So minfree = (max(960,(120 * 12)/3)) = 1440 / 3 = 480 or 960 whichever is larger
And maxfree = minfree + (128 * 12) / 3 = 960 + 512 = 1472

I would probably bump this to 1536 rather than using 1472 (nice power of 2)

If you over allocate these values it is possible that you will see high values in the “fre” column of a vmstat and yet you will be paging.

40
 svmon
# svmon -G -O unit=auto -i 2 2

Unit: auto
--------------------------------------------------------------------------------------
size inuse free pin virtual available mmode
memory 8.00G 3.14G 4.86G 2.20G 2.57G 5.18G Ded-E
pg space 4.00G 10.5M

work pers clnt other

pin 1.43G 0K 0K 794.95M
in use 2.57G 0K 589.18M
Unit: auto
--------------------------------------------------------------------------------------
size inuse free pin virtual available mmode
memory 8.00G 3.14G 4.86G 2.20G 2.57G 5.18G Ded-E
pg space 4.00G 10.5M

work pers clnt other

pin 1.43G 0K 0K 794.95M
in use 2.57G 0K 589.18M

41
 svmon
# svmon -G -O unit=auto,timestamp=on,pgsz=on,affinity=detail -i 2 2

Unit: auto Timestamp: 16:27:26

--------------------------------------------------------------------------------------
size inuse free pin virtual available mmode
memory 8.00G 3.14G 4.86G 2.20G 2.57G 5.18G Ded-E
pg space 4.00G 10.4M

work pers clnt other

pin 1.43G 0K 0K 794.95M
in use 2.57G 0K 589.16M

Domain affinity free used total filecache lcpus

0 4.86G 2.37G 7.22G 567.50M 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Unit: auto Timestamp: 16:27:28

--------------------------------------------------------------------------------------
size inuse free pin virtual available mmode
memory 8.00G 3.14G 4.86G 2.20G 2.57G 5.18G Ded-E
pg space 4.00G 10.4M

work pers clnt other

pin 1.43G 0K 0K 794.95M
in use 2.57G 0K 589.16M

Domain affinity free used total filecache lcpus

0 4.86G 2.37G 7.22G 567.50M 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

42
 NETWORK
See article at:
http://www.ibmsystemsmag.com/aix/administrator/networks/network_tuning/

43
 Starter set of tunables 3

Typically we set the following for both versions:

NETWORK
no -p -o rfc1323=1
no -p -o tcp_sendspace=262144
no -p -o tcp_recvspace=262144
no -p -o udp_sendspace=65536
no -p -o udp_recvspace=655360

Also check the actual NIC interfaces and make sure they are set to at least these values

Check sb_max is at least 1040000 – increase as needed

44
 ifconfig
ifconfig -a output

en0:
flags=1e080863,480<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACT
IVE),CHAIN>
inet 10.2.0.37 netmask 0xfffffe00 broadcast 10.2.1.255
tcp_sendspace 65536 tcp_recvspace 65536 rfc1323 0
lo0: flags=e08084b<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1

These override no, so they will need to be set at the adapter.

Additionally you will want to ensure you set the adapter to the correct setting if it runs at less than GB, rather than allowing
auto-negotiate

Stop inetd and use chdev to reset adapter (i.e. en0)

Or use chdev with the –P and the changes will come in at the next reboot
chdev -l en0 -a tcp_recvspace=262144 –a tcp_sendspace=262144 –a rfc1323=1 –P

On a VIO server I normally bump the transmit queues on the real (underlying adapters) for the aggregate/SEA
Example for a 1Gbe adapter:
chdev -l ent? -a txdesc_que_sz=1024 -a tx_que_sz=16384 -P

45
 My VIO Server SEA
# ifconfig -a
en6:
flags=1e080863,580<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,6
4BIT,CHECKSUM_OFFLOAD(ACTIVE),CHAIN>

inet 192.168.2.5 netmask 0xffffff00 broadcast 192.168.2.255

tcp_sendspace 262144 tcp_recvspace 262144 rfc1323 1

lo0:
flags=e08084b,1c0<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BI
T,LARGESEND,CHAIN>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1%1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1

46
 Network
Interface Speed MTU tcp_sendspace tcp_recvspace rfc1323

lo0 N/A 16896 131072 131072 1

Ethernet 10/100 mb
Ethernet 1000 (Gb) 1500 131072 165536 1
Ethernet 1000 (Gb) 9000 262144 131072 1
Ethernet 1000 (Gb) 1500 262144 262144 1
Ethernet 1000 (Gb) 9000 262144 262144 1
Virtual Ethernet N/A any 262144 262144 1
InfiniBand N/A 2044 131072 131072 1

Above taken from Page 247 SC23-4905-04 November 2007 edition

Check up to date information at:
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.prftungd/doc/prftungd/prftungd.pdf

AIX v6.1
http://publib.boulder.ibm.com/infocenter/aix/v6r1/topic/com.ibm.aix.prftungd/doc/prftungd/prftungd_pdf.pdf

47
 Network Commands
• entstat –d or netstat –v (also –m and –I)
• netpmon
• iptrace (traces) and ipreport (formats trace)
• Tcpdump
• traceroute
• chdev, lsattr
• no
• ifconfig
• ping and netperf
• ftp
• Can use ftp to measure network throughput
• ftp to target
• ftp> put “| dd if=/dev/zero bs=32k count=100” /dev/null
• Compare to bandwidth (For 1Gbit - 948 Mb/s if simplex and 1470 if duplex )
• 1Gbit = 0.125 GB = 1000 Mb = 100 MB) but that is 100%

48
 Net tab in nmon

49
 Other Network
• If 10Gb network check out Gareth’s Webinar
• https://www.ibm.com/developerworks/wikis/download/attachments/153124943/7_PowerVM_10Gbit_Ethernet.pdf?version=1
• netstat –v
• Look for overflows and memory allocation failures
Max Packets on S/W Transmit Queue: 884
S/W Transmit Queue Overflow: 9522
• “Software Xmit Q overflows” or “packets dropped due to memory allocation failure”
• Increase adapter xmit queue
• Use lsattr –EL ent? To see setting
• Look for receive errors or transmit errors
• dma underruns or overruns
• mbuf errors
• lparstat 2
• Look for high vcsw – indicator that entitlement may be too low
• tcp_nodelay (or tcp_nodelayack)
• Disabled by default
• 200ms delay by default as it waits to piggy back TCP acks onto response packets
• Tradeoff is more traffic versus faster response
• Also check errpt – people often forget this

50
 entstat -v
ETHERNET STATISTICS (ent18) :
Device Type: Shared Ethernet Adapter
Elapsed Time: 44 days 4 hours 21 minutes 3 seconds
Transmit Statistics: Receive Statistics:
-------------------- -------------------
Packets: 94747296468 Packets: 94747124969
Bytes: 99551035538979 Bytes: 99550991883196
Interrupts: 0 Interrupts: 22738616174
Transmit Errors: 0 Receive Errors: 0
Packets Dropped: 0 Packets Dropped: 286155
Bad Packets: 0
Max Packets on S/W Transmit Queue: 712
S/W Transmit Queue Overflow: 0
Current S/W+H/W Transmit Queue Length: 50

Elapsed Time: 0 days 0 hours 0 minutes 0 seconds

Broadcast Packets: 3227715 Broadcast Packets: 3221586
Multicast Packets: 3394222 Multicast Packets: 3903090
No Carrier Sense: 0 CRC Errors: 0
DMA Underrun: 0 DMA Overrun: 0
Lost CTS Errors: 0 Alignment Errors: 0
Max Collision Errors: 0 No Resource Errors: 286155 check those tiny, etc Buffers
Late Collision Errors: 0 Receive Collision Errors: 0
Deferred: 0 Packet Too Short Errors: 0
SQE Test: 0 Packet Too Long Errors: 0
Timeout Errors: 0 Packets Discarded by Adapter: 0
Single Collision Count: 0 Receiver Start Count: 0
Multiple Collision Count: 0
Current HW Transmit Queue Length: 50

51
 entstat –v vio
SEA
Transmit Statistics: Receive Statistics:
-------------------- -------------------
Packets: 83329901816 Packets: 83491933633
Bytes: 87482716994025 Bytes: 87620268594031
Interrupts: 0 Interrupts: 18848013287
Transmit Errors: 0 Receive Errors: 0
Packets Dropped: 0 Packets Dropped: 67836309
Bad Packets: 0
Max Packets on S/W Transmit Queue: 374
S/W Transmit Queue Overflow: 0
Current S/W+H/W Transmit Queue Length: 0

Elapsed Time: 0 days 0 hours 0 minutes 0 seconds

Broadcast Packets: 1077222 Broadcast Packets: 1075746
Multicast Packets: 3194318 Multicast Packets: 3194313
No Carrier Sense: 0 CRC Errors: 0
DMA Underrun: 0 DMA Overrun: 0
Lost CTS Errors: 0 Alignment Errors: 0
Max Collision Errors: 0 No Resource Errors: 67836309

Virtual I/O Ethernet Adapter (l-lan) Specific Statistics:

---------------------------------------------------------
Hypervisor Send Failures: 4043136
Receiver Failures: 4043136 “No Resource Errors” can occur when the appropriate amount of
Send Errors: 0 memory can not be added quickly to vent buffer space for a
Hypervisor Receive Failures: 67836309 workload situation.

52
52
 Buffers
Virtual Trunk Statistics
Receive Information
Receive Buffers
Buffer Type Tiny Small Medium Large Huge
Min Buffers 512 512 128 24 24
Max Buffers 2048 2048 256 64 64
Allocated 513 2042 128 24 24
Registered 511 506 128 24 24
History
Max Allocated 532 2048 128 24 24
Lowest Registered 502 354 128 24 24

“Max Allocated” represents the maximum number of buffers ever allocated

“Min Buffers” is number of pre-allocated buffers
“Max Buffers” is an absolute threshhold for how many buffers can be allocated

chdev –l <veth> -a max_buf_small=4096 –P

chdev –l <veth> -a min_buf_small=2048 –P
Above increases min and max small buffers for the virtual ethernet adapter configured for the SEA above
Needs a reboot

53
53
 nmon Monitoring

• nmon -ft –AOPV^dMLW -s 15 -c 120

• Grabs a 30 minute nmon snapshot
• A is async IO
• M is mempages
• t is top processes
• L is large pages
• O is SEA on the VIO
• P is paging space
• V is disk volume group
• d is disk service times
• ^ is fibre adapter stats
• W is workload manager statistics if you have WLM enabled
If you want a 24 hour nmon use:
nmon -ft –AOPV^dMLW -s 150 -c 576
May need to enable accounting on the SEA first – this is done on the VIO
chdev –dev ent* -attr accounting=enabled
Can use entstat/seastat or topas/nmon to monitor – this is done on the vios
topas –E
nmon -O
VIOS performance advisor also reports on the SEAs

54
 Useful Links
• Nigel on Entitlements and VPs plus 7 most frequently asked questions
• http://www.youtube.com/watch?v=1W1M114ppHQ&feature=youtu.be
• Charlie Cler Articles
• http://www.ibmsystemsmag.com/authors/Charlie-Cler/
• Andrew Goade Articles
• http://www.ibmsystemsmag.com/authors/Andrew-Goade/
• Jaqui Lynch Articles
• http://www.ibmsystemsmag.com/authors/Jaqui-Lynch/
• Jay Kruemke Twitter – chromeaix
• https://twitter.com/chromeaix
• Nigel Griffiths Twitter – mr_nmon
• https://twitter.com/mr_nmon
• Jaqui’s Upcoming Talks and Movies
• Upcoming Talks
• http://www.circle4.com/forsythetalks.html
• Movie replays
• http://www.circle4.com/movies

55
 Useful Links
• Nigel Griffiths
• AIXpert Blog
• https://www.ibm.com/developerworks/mydeveloperworks/blogs/aixpert/?lang=en
• 10 Golden rules for rPerf Sizing
• https://www.ibm.com/developerworks/mydeveloperworks/blogs/aixpert/entry/size_with_rperf_if_you_
must_but_don_t_forget_the_assumptions98?lang=en
• Youtube channel
• http://www.youtube.com/user/nigelargriffiths

• AIX Wiki
• https://www.ibm.com/developerworks/wikis/display/WikiPtype/AIX
• HMC Scanner
• http://www.ibm.com/developerworks/wikis/display/WikiPtype/HMC+Scanner
• Workload Estimator
• http://ibm.com/systems/support/tools/estimator
• Performance Tools Wiki
• http://www.ibm.com/developerworks/wikis/display/WikiPtype/Performance+Monitoring+Tools
• Performance Monitoring
• https://www.ibm.com/developerworks/wikis/display/WikiPtype/Performance+Monitoring+Documentation
• Other Performance Tools
• https://www.ibm.com/developerworks/wikis/display/WikiPtype/Other+Performance+Tools
• Includes new advisors for Java, VIOS, Virtualization
• VIOS Advisor
• https://www.ibm.com/developerworks/wikis/display/WikiPtype/Other+Performance+Tools#OtherPerformance
Tools-VIOSPA

56
 References
• Simultaneous Multi-Threading on POWER7 Processors by Mark Funk
• http://www.ibm.com/systems/resources/pwrsysperf_SMT4OnP7.pdf
• Processor Utilization in AIX by Saravanan Devendran
• https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Power%20Systems/p
age/Understanding%20CPU%20utilization%20on%20AIX
• Rosa Davidson Back to Basics Part 1 and 2 –Jan 24 and 31, 2013
• https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Power%20Systems/page/AIX%20Virtual%20
User%20Group%20-%20USA
• Nigel – PowerVM User Group
• https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Power%20Systems/page/PowerVM%20techn
ical%20webinar%20series%20on%20Power%20Systems%20Virtualization%20from%20IBM%20web
• SG24-7940 - PowerVM Virtualization - Introduction and Configuration
• http://www.redbooks.ibm.com/redbooks/pdfs/sg247940.pdf
• SG24-7590 – PowerVM Virtualization – Managing and Monitoring
• http://www.redbooks.ibm.com/redbooks/pdfs/sg247590.pdf
• SG24-8080 – Power Systems Performance Guide – Implementing and Optimizing
• http://www.redbooks.ibm.com/redbooks/pdfs/sg248080.pdf
• SG24-8079 – Power 7 and 7+ Optimization and Tuning Guide
• http://www.redbooks.ibm.com/redbooks/pdfs/sg248079.pdf
• Redbook Tip on Maximizing the Value of P7 and P7+ through Tuning and Optimization
• http://www.redbooks.ibm.com/technotes/tips0956.pdf

57
 Thank you for your time

If you have questions please email me at:

lynchj@forsythe.com

Download latest presentation at the AIX Virtual User Group site:

http://www.tinyurl.com/ibmaixvug

Also check out the UK PowerVM ser group at:

http://tinyurl.com/PowerSystemsTechnicalWebinars

58