Progress - RDBMS Tuning - Radius

OpenEdge 10 RDBMS 

Performance Tuning 

Simon Epps, Progress Software

Progress Software Corporation 

Application Infrastructure Software 

Used to develop, deploy, integrate and manage 

business applications 

Server-centric Client-server Web SOA 

5,000 Applications 

generating 

$5B Annual Revenue 

40% 

Direct 

60% 

Partner 

North America 46% 

Latin America 5% 

Asia/Pacific 6% 

EMEA 43% 

Software Business 

FY07 $494 

Offices 90 world wide 

Founded 1981 

Progress Community 140 Countries 24 Years of Experience 

Deployed at 120,000 sites in 70,000 organizations for over 5 million users 

© Copyright Radius Solutions 2007 All Rights Reserved 2

Progress OpenEdge – Unique Relationships 

Over 1,500 Application Partners Worldwide 


Leading Application Infrastructure Products 

OpenEdge 

Apama 

Sonic 

Actional 

Shadow 

DataXtend 

EasyAsk 

DataDirect 

ObjectStore 

Business Application Platform 

Event Stream Processing Platform 

Enterprise Service Bus 

SOA & Web Services Management 

Mainframe Integration 

Data Integration 

Natural Language Search and Query 

Data Connectivity 

Object Data Management 

Application Platforms 

Services Infrastructure 

Data Infrastructure 


Objective 

Review general 

Database tuning and 

emphasize OpenEdge 

10 performance features 


Tuning Tips 

Establishing harmony 

– CPU 

– Memory 

– I/O bandwidth 

– Contention/Conflict resolution 

– Scientific method 


Agenda 

Physical Setup 

Effect of Startup Parameters 

What To Do at Runtime 

Faster Maintenance 


Physical Layout 

File Extent location 

– Separate disks for data, bi and ai files 

– Separate Index/tables 

– Group similar tables 

– Bi on disk with fastest I/O rate 

Use RAID striping or do it yourself 

Spread I/O amongst hardware spindles 


i Blocksize 

proutil -C truncate bi –biblocksize 

Size of before image block (1, 2, 4, 8, 16 K) 

– Default size: 8 K 

Reduce overhead & improve I/O efficiency 

Dictates I/O and bi buffer page size 

Ai block size should match bi block size 

Decreases cluster closes 

Balance bi partial writes with bi full writes 


i Cluster Size 

proutil -C truncate bi –bi 

# of Kbytes in cluster (for checkpointing) 

– Must be a multiple of 16 

– Default: 512 Max: 16383 

Fewer checkpoints improve performance 

Increase size when checkpoints < 2 minutes 

Drawbacks 

– Increased recovery time 

– Increased bi disk space 

– Longer checkpoint time 


Database Blocksize 

prostrct create -blocksize 

Size of database block 

– Default size: Unix – 1K, Windows – 4K 

– Valid sizes: 1024, 2048, 4096, 8192 

– Should match file system page size 

Reduce overhead & improve I/O efficiency 

Dictates I/O and buffer pool page size 

Coordinate with RPB and -B 


Type II Storage Areas 

Block clustering for data areas 

– Alleviates object fragmentation/scatter 

– Improves I/O efficiency 

Concurrent Hierarchical Space Allocation 

– Area space Allocation 

– Object space allocation 

Improved object manipulation 

– Table scan without index 

– Fast object deletion 


Object Placement 

Same area 

– Space allocation awareness 

• Cluster size allocation 

• Records per block 

• Fragmentation and scatter 

– I/O considerations 

Separate areas 

– Static vs. dynamic data 

– I/O considerations 


Agenda 






Latching: -spin 

Number of busy latch retries before nap 

SMP machines: # of CPU * 5,000 

Lower if CPU usage increases > 90% 

Decrease latch timeouts 

More timeout means more napping 

– Nap default is 10ms & doubled up to ½ sec 

Can change –spin online via promon 


Latching: -semsets 

Indicates arrays of semaphores 

Performance gain is OS dependant 

d 

Semaphores handed out round robin 

Specify when there are many connections (> 1000) 


Buffers: –B 

Number of entries in database buffer pool 

Value in database block size units 

– Default size: single user – 102 

Reduces database I/O 

multi user - # clients * 8 + 2 

Increase when buffer hit ratio < 90% 

Too many buffers may cause O/S paging 

g 

Increase performance by decreasing database I/O 


Buffers: -hash 

Size of buffer pool hash table 

Limits i # of lookups for buffer retrieval 

Typically prime > ¼ (-B) in geometric progression 

with ratio ~1.4 

Specify explicitly when –B > 400,000 


Buffers: -bibufs 

Number of buffers in bi buffer pool 

Value in bi block size units 

– Defaults: single user – 3 multi user – 5 suggest 25 

Reduced bi buffer contention 

Increase if any empty buffer waits 

– No bi buffers available 

-aibufs should match –bibufs 


Buffers: -Bp (Read Only Buffers) 

Specify private LRU chain 

Will not effect –B LRU chain on reads 

Set at runtime via _myConnection 

– _MyConn-NumSeqBuffers 

Use when performing table scans 

– Now works for Backup too! 

-Bpmax 

– broker over ride max of 64/user 

– will not override limit of 25% -B 


Buffers: -omsize 

# of entries in object mapping cache 

Om cache maintains i LRU for replacement 

LRU avoided if –omsize appropriate 

Default: 1024 

select count(*) from _storageobject 


Buffers: -omsize 

Omlru avoidance when –omsize proper (default: 1024) 

Find I1/T1 

Find I2/T2 

Find I3/T3 

Find I1/T1 

Find I2 … 

aging 

replacing 

Hash 

Table 

“newest” 

LRU Chain 

“oldest” 

T1 I1 T3 I3 T2 I2 T4 I4 

Area 6 Area 7 Area 8 Area 9 


Buffers: -Bt 

Temp Tables use Type II Storage Areas 

– Fast empty/drop 

– Use “empty temp-table ” 

– Mitigate space overhead with –Bt 

– -tmpbsize 1 or -tmpbsize 8 

• Records per block 

• Create/toss limit 

• Possible wasted space 

• Additional block format overhead 


Others: 

-Mm 

– increases network message buffer size 

– decreases # network message packets 

– MUST match between client and server 

– Default 1024 

-pinshm 

– Avoids paging g of shared memory 

– off by default 


Agenda 






Before Image Writer 

Writes filled bi buffers to disk 

Avoids writing i bi buffers by server 

One per database maximum 

Decreases empty buffer waits 

Every database should have one 


Asynchronous Page Writers 

Writes dirty database pages to disk 

Avoids writes by servers 

Reduces checkpoint time 

May also flush bi and ai buffers 

Decreases LRU writes 

Increase until 0 blocks flushed at checkpoint and 

partial bi writes low 


Watch Dog 

Monitors for dead processes 

Performs cleanup 

Lightens load of Database Broker 


Look out for… 

Scatter factor 

– Describe what it is 

– 3.5 to 4 indicates dump and load time 

Fragmentation Factor > 2 indicates D&L 

Fixed Data Extents 

Use promon 

– I/O rates 

– Buffers flushed at checkpoint 

– Time between checkpoints 

– Buffer Hit ratio 

– Contention (buffers, locks, latches) 


Agenda 






Index Rebuild 

Index Rebuild by area, table or schema 

proutil -C idxbuild table 

• Typical Uses: 

• complete D&L process 

• Bring deactive indexes online 

• Fix corruption 

• Always sort when asked (if you have the temp 

space) 


Idxbuild – Sort Groups 

# of sort groups 

-SG: 8 thru 64 – Default: 48 

A larger -SG performs less sort/merge(s) 

Databases with many indexes per area use larger 

SG values 

Other values 

– -TM 32 (merge buffers) 

– -TB 24 (temp block size) 

– -T specify a different disk 


Index Compaction 

proutil -C idxcompact [ n ] 

When to run 

– Compact index when %utilization < 60% 

– suggest value of 80% to 90% 

– 100% may cause expensive index block splits 

Can be run online 


Other Utilities 

proutil -C dump –index 0 

– Dump performance over data order 

– Or choose index based on read order 

– Load to truncated t area 

• (truncate rather than “emptied”) 

Run online backup with –Bp 


Questions 

& Thank you for 

your time

Progress - RDBMS Tuning - Radius

Create successful ePaper yourself

Delete template?

Save as template?