(zOS V10) Compression Options

Alan Gredell

(zOS V10) Compression Options

Our DBA's were recently given the mission to add DB2 compression to several hundred production tables that met some reasonable criteria.  However, as we near completion of the mission, we were tagged by our performance group for spiking our 4HRA (4 Hour Rolling Average, used to determine billing amounts for several types of tools) by running the REORG to "activate" the compression.  Hence, we started including the performance group as approvers of our change.  Lo and behold, one of them said "we have just installed zEDC cards, and were going to turn them on soon".  We are uncertain whether to continue with our DB2 compression mission, or undo all of our previous work (and then some, as we had compressed some tablespaces previously).  Mr. Performance showed us a couple of graphs that make it pretty clear that the hardware works better quite often.  What's this group's experience with one, or both, of these, both individually, and with BOTH implemented?  Are we needlessly spending cycles compressing and decompressing stuff that will be better off  under zEDC compression alone?  Your esteemed input, as always, is quite welcomed! 

Venkat Srinivasan

RE: (zOS V10) Compression Options
(in response to Alan Gredell)

DB2 tablespace compression is with cmpsc and done by cpu and co-processor. zEDC uses a pci-e card. They are distinct items. I am reasonably sure cmpsc does not use zEDC when the card is installed. I will stand corrected if told otherwise. zEDC utilizes zlib oriented deflate standard.

Venkat

In Reply to Alan Gredell:

Our DBA's were recently given the mission to add DB2 compression to several hundred production tables that met some reasonable criteria.  However, as we near completion of the mission, we were tagged by our performance group for spiking our 4HRA (4 Hour Rolling Average, used to determine billing amounts for several types of tools) by running the REORG to "activate" the compression.  Hence, we started including the performance group as approvers of our change.  Lo and behold, one of them said "we have just installed zEDC cards, and were going to turn them on soon".  We are uncertain whether to continue with our DB2 compression mission, or undo all of our previous work (and then some, as we had compressed some tablespaces previously).  Mr. Performance showed us a couple of graphs that make it pretty clear that the hardware works better quite often.  What's this group's experience with one, or both, of these, both individually, and with BOTH implemented?  Are we needlessly spending cycles compressing and decompressing stuff that will be better off  under zEDC compression alone?  Your esteemed input, as always, is quite welcomed! 

Chris Tee

(zOS V10) Compression Options
(in response to Alan Gredell)
Alan


DB2 data compression cannot use the zEDC feature, it uses the CMPSC instruction so you still need COMPRESS YES on the tablespaces you want to compress. zEDC can be used, via SMS DATACLAS, to compress archive logs and image copy datasets(even if the data is already compressed via DB2 compression).


Chris


________________________________
From: Alan Gredell <[login to unmask email]>
Sent: 01 March 2017 21:21
To: [login to unmask email]
Subject: [DB2-L] - (zOS V10) Compression Options


Our DBA's were recently given the mission to add DB2 compression to several hundred production tables that met some reasonable criteria. However, as we near completion of the mission, we were tagged by our performance group for spiking our 4HRA (4 Hour Rolling Average, used to determine billing amounts for several types of tools) by running the REORG to "activate" the compression. Hence, we started including the performance group as approvers of our change. Lo and behold, one of them said "we have just installed zEDC cards, and were going to turn them on soon". We are uncertain whether to continue with our DB2 compression mission, or undo all of our previous work (and then some, as we had compressed some tablespaces previously). Mr. Performance showed us a couple of graphs that make it pretty clear that the hardware works better quite often. What's this group's experience with one, or both, of these, both individually, and with BOTH implemented? Are we needlessly spending cycles compressing and decompressing stuff that will be better off under zEDC compression alone? Your esteemed input, as always, is quite welcomed!

-----End Original Message-----

Daniel Luksetich

(zOS V10) Compression Options
(in response to Chris Tee)
And LOBs in DB2 12!

Dan



Daniel L Luksetich

DanL Database Consulting



IBM GOLD Consultant

IBM Champion for Analytics

IDUG Content Committee Chairman

IBM Certified Database Adminstrator - DB2 11 DBA for z/OS

IBM Certified System Administrator - DB2 11 for z/OS

IBM Certified Application Developer - DB2 11 for z/OS

IBM Certified Advanced Database Administrator - DB2 10.1 for Linux UNIX and
Windows



From: Chris Tee [mailto:[login to unmask email]
Sent: Thursday, March 2, 2017 5:29 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: (zOS V10) Compression Options



Alan



DB2 data compression cannot use the zEDC feature, it uses the CMPSC
instruction so you still need COMPRESS YES on the tablespaces you want to
compress. zEDC can be used, via SMS DATACLAS, to compress archive logs and
image copy datasets(even if the data is already compressed via DB2
compression).



Chris



_____

From: Alan Gredell <[login to unmask email] <mailto:[login to unmask email]> >
Sent: 01 March 2017 21:21
To: [login to unmask email] <mailto:[login to unmask email]>
Subject: [DB2-L] - (zOS V10) Compression Options



Our DBA's were recently given the mission to add DB2 compression to several
hundred production tables that met some reasonable criteria. However, as we
near completion of the mission, we were tagged by our performance group for
spiking our 4HRA (4 Hour Rolling Average, used to determine billing amounts
for several types of tools) by running the REORG to "activate" the
compression. Hence, we started including the performance group as approvers
of our change. Lo and behold, one of them said "we have just installed zEDC
cards, and were going to turn them on soon". We are uncertain whether to
continue with our DB2 compression mission, or undo all of our previous work
(and then some, as we had compressed some tablespaces previously). Mr.
Performance showed us a couple of graphs that make it pretty clear that the
hardware works better quite often. What's this group's experience with one,
or both, of these, both individually, and with BOTH implemented? Are we
needlessly spending cycles compressing and decompressing stuff that will be
better off under zEDC compression alone? Your esteemed input, as always,
is quite welcomed!



-----End Original Message-----



-----End Original Message-----

Alan Gredell

RE: (zOS V10) Compression Options
(in response to Venkat Srinivasan)

Thanks, Venkat, but I don't detect an answer in your reply.  Is it reasonable or smart to use both types of compression? My inclination is to think it is not, that either one will do, and since the zEDC card does not use CPU cycles on the mainframe to perform it's compression, that would be the wiser choice.  BTW, I appreciate your many wise replies on this forum!

Alan Gredell

RE: (zOS V10) Compression Options
(in response to Venkat Srinivasan)

Please ignore my question, Venkat, while online I noticed Chris's reply, so that answer is now clear. 

Myron Miller

(zOS V10) Compression Options
(in response to Daniel Luksetich)

YEAH!!!! Finally.about time.


Thanks Myron W. Miller
________________________________
From: Daniel L Luksetich <[login to unmask email]>
Sent: Thursday, March 2, 2017 8:58:25 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: (zOS V10) Compression Options


And LOBs in DB2 12!

Dan



Daniel L Luksetich

DanL Database Consulting



IBM GOLD Consultant

IBM Champion for Analytics

IDUG Content Committee Chairman

IBM Certified Database Adminstrator – DB2 11 DBA for z/OS

IBM Certified System Administrator – DB2 11 for z/OS

IBM Certified Application Developer – DB2 11 for z/OS

IBM Certified Advanced Database Administrator – DB2 10.1 for Linux UNIX and Windows



From: Chris Tee [mailto:[login to unmask email]
Sent: Thursday, March 2, 2017 5:29 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: (zOS V10) Compression Options



Alan



DB2 data compression cannot use the zEDC feature, it uses the CMPSC instruction so you still need COMPRESS YES on the tablespaces you want to compress. zEDC can be used, via SMS DATACLAS, to compress archive logs and image copy datasets(even if the data is already compressed via DB2 compression).



Chris



________________________________

From: Alan Gredell <[login to unmask email]<mailto:[login to unmask email]>>
Sent: 01 March 2017 21:21
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - (zOS V10) Compression Options



Our DBA's were recently given the mission to add DB2 compression to several hundred production tables that met some reasonable criteria. However, as we near completion of the mission, we were tagged by our performance group for spiking our 4HRA (4 Hour Rolling Average, used to determine billing amounts for several types of tools) by running the REORG to "activate" the compression. Hence, we started including the performance group as approvers of our change. Lo and behold, one of them said "we have just installed zEDC cards, and were going to turn them on soon". We are uncertain whether to continue with our DB2 compression mission, or undo all of our previous work (and then some, as we had compressed some tablespaces previously). Mr. Performance showed us a couple of graphs that make it pretty clear that the hardware works better quite often. What's this group's experience with one, or both, of these, both individually, and with BOTH implemented? Are we needlessly spending cycles compressing and decompressing stuff that will be better off under zEDC compression alone? Your esteemed input, as always, is quite welcomed!



-----End Original Message-----



-----End Original Message-----

-----End Original Message-----