EnterpriseOne and Database Compression

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 1 EXPERIENCE. INNOVATION. ©2013 Velocity Technology Solutions, Inc.

Paul Shearer, Velocity, JD Edwards Solution Engineer

Session 101100: Database Compression for JD Edwards

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 2

Agenda

• What is DB compression? • How does DB compression work?

• What are the benefits of DB compression for EnterpriseOne?

• Which database editions support compression?

• Case Studies!


What is DB Compression?

DB compression is like converting English text into Chinese. 压缩就像是将英文文本转换成中国人 English = 59 characters Chinese = 16 characters “Compression uses symbols to replace long, reoccurring patterns.”


Oracle Compression


SQL Compression

• Column Prefix Compression – Find repeating ‘byte pattern’ in the same column in the same

data page

• Dictionary Page Compression – Find repeating ‘byte patterns’ across columns within the same

data page


Column Prefix Compression


Benefits of DB Compression for E1

• Disk space reduction – 60% to 70% for Oracle DBs – 70% to 90% reduction for SQL DBs

• Lower RAM requirements for the DBMS*

– Data pages are cached in RAM – Increase Buffer-hit-cache ratio – Fewer physical disk IOs

• 50+% performance gains on EnterpriseOne performance

– Each physical read operation returns more data


DB Requirements for Compression

• SQL Enterprise Edition

– 2008 and higher

• Oracle Enterprise Edition + Feature – 11G and higher


JDE Test Environment

• Server – OracleVM 2.1.2

– Oracle Enterprise Linux 5 64 bits Paravirtualized

– 4 cores & 16 GB of memory

• Oracle Database – Oracle DB 11g Enterprise Edition (11.1.0.7)

– Block Size: 8K (default)

– Memory Target (SGA + PGA): 12 GB


JDE Test - Implementation

• Created a separated compressed tablespace

• Moved top tables to new tablespace

• Utilized compress for all operations

• Leveraged online redefinition to move data

• Compared results before and after compression


Test Results – Disk Space

0

200

400

600

800

1000

1200

MB

Storage Utilization

Uncompressed Compressed

~60% Storage Savings


Test Results – Read Performance

200

300

400

500

600

700

800

Time (seconds)

Read Performance - Full Scans


Compression is 2.7x Faster


Test Results – Write Performance

20000

21000

22000

23000

Time (seconds)

DML Performance - Inserts


Compression has ~1% Overhead


Test Results – Write Performance

20000

21000

22000

23000

Time (seconds)

DML Performance - Updates


Compression has ~2% Overhead


Sample Compression Rates

Table Name Compression

F4111 Item Ledger File 76%

F0911 Account Ledger 73%

F0411 Accounts Payable Ledger 69%

F43121 Purchase Order Receiver File 69%

F4311 Purchase Order Detail File 68%

F9000 Task Master 62%

F0101 Address Book Master 61%

F4229 Sales Summary History File 56%

F0005 User Defined Code Types 54%


SQL Compression Lab Project Results


Environment • IBM 3850 M3

• 128gb RAM • 16 Cores

• SQL 2008 Enterprise x64 SP1 • 47.5gb memory allocated • Parallelism = 1

• Storage • EMC San DMX 4 • Dual Attached • 64kb NTFS Allocation Size • 64kb Disk Offset

• Database • JDE_PRODUCTION (162gb)

Slide 18


Implementation • Restored JDE_PRODUCTION to SQL2008POC on SQL21 and created three

databases • Uncompressed • Row Compression – 2 hours 9 minutes to compress • Page Compression – 2 hours 21 minutes to compress

• Captured a 1 hour long profile trace from SQL20 for JDE_PRODUCTION • 231 sql connections

• Replayed profile trace against all three of the databases and captured stats • SQL 2008 DMV’s • Windows Perfmon • Red-Gate


Slide 20

Database Size

162

64

16

0

20

40

60

80

100

120

140

160

180

Uncompressed Row Compression Page Compression

Size

in G

B

Compression Type

Database Sizes

~90% Reduction in Storage Needed


Slide 21

Database Backup Size

15.3

6.9

5

0

2

4

6

8

10

12

14

16

18


Size

in G

B

Compression Type

Backup Sizes

~67% Reduction in Backup Storage

Needed


Slide 22

Backup Times

24

5.5

1.5

0

5

10

15

20

25

30


Min

utes

Compression Type

Backup Times

~93% Reduction in Backup Times


Slide 23

24

5.5

1.5

0

5

10

15

20

25

30


Min

utes

Compression Type

Restore Times

~81% Reduction in Restore Times

Restore Times


Slide 24

Number of Reads

45671

16238

10721

0

5000

10000

15000

20000

25000

30000

35000

40000

45000

50000


Read

s

Compression Type

Number of Reads

~76% Reduction in Number of Reads


Slide 25

Read Time

3995

502 266

0

500

1000

1500

2000

2500

3000

3500

4000

4500


Seco

nds

Compression Type

Read Time (Seconds)

~93% Reduction in Read Time


Slide 26

Number of Writes

20792

20272

18386

17000

17500

18000

18500

19000

19500

20000

20500

21000


Writ

es

Compression Type

Number of Writes

~11% Reduction in Number of Writes


Slide 27

Write Time

220

165 154

0

50

100

150

200

250


Seco

nds

Compression Type

Write Time (Seconds)

~24% Reduction in Write Time


Slide 28

CPU Utilization

15.52862204

16.80666781

16.38710853

14.5

15

15.5

16

16.5

17


Perc

ent

Compression Type

Percent CPU Time

~8% Increase in Percent CPU Time

Used


Memory Utilization

2164773.926

743887.2381 576674.3415

0

500000

1000000

1500000

2000000

2500000


MB

Allo

cate

d

Compression Type

Memory Utilization

~73% Reduction in Memory Needed


Slide 30

Buffer Cache Hit Ratio

94.46759604

96.52317432

97.40602574

92.5

93

93.5

94

94.5

95

95.5

96

96.5

97

97.5

98


Perc

ent

Compression Type

Buffer Cache Hit Ratio

~3% Increase in Buffer Cache Hit

Ratio


Slide 31

Disk Utilization

0.021782055

0.014864164 0.015834584

0

0.005

0.01

0.015

0.02

0.025


Perc

ent

Compression Type

Avg. Disk sec/Transfer

~33% Decrease in Disk Transfer Time


Slide 32

Top 5 LRQ - Duration

180.92578

86.04883 71.97558

0

20

40

60

80

100

120

140

160

180

200


Seco

nds

Compression Type

Top 5 LRQ – Duration (Seconds)

~60% Reduction in Duration


Slide 33

Top 5 LRQ – CPU Time (ms)

49.43

40.44629

33.87402

0.00

10.00

20.00

30.00

40.00

50.00

60.00


Seco

nds

Compression Type

Top 5 LRQ - CPU Time (Seconds)

~31% Reduction in CPU Time


Slide 34

Top 5 LRQ – Physical Reads

20588

7063

4547

0

5000

10000

15000

20000

25000


Phys

ical

Rea

ds

Compression Type

Top 5 LRQ - Physical Reads

~77% Reduction in Physical Reads


Slide 35

Top 5 LRQ - Writes

4617

5302

4204

0

1000

2000

3000

4000

5000

6000


Writ

es

Compression Type

Top 5 LRQ - Writes

~9% Reduction in Writes


Slide 36

Notes • Recommended Indexes

• Index’s are used more efficiently when the DB is compressed • Uncompressed – 40 new indexes were recommended • Row Compression – 26 new indexes were recommended • Page Compression – 16 new indexes were recommended


International Footprint to Serve Our Customers

Denver, Colorado

Seattle, Washington

London, Ontario

Temple Terrace, Florida

Minneapolis, Minnesota Tukwila, Washington

New York, New York

Glasgow, Scotland


Velocity Is an Active Member of the Oracle® Community

Built first hosted JD Edwards solution

Customers with operations in 25 countries

Support for Oracle edge

apps and other partner

software

Expertise in JD Edwards, E-Business,

Hyperion and others

40+ employees Oracle /

JD Edwards certified


Questions?

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 40 EXPERIENCE. INNOVATION. ©2013 Velocity Technology Solutions, Inc.

Thank you. For more information:

[email protected]

803-386-9680

EnterpriseOne and Database Compression

Education

Transcript of EnterpriseOne and Database Compression