When another acronym shows up it usually means something new. These technology advances continue to improve mainframe processing. However, sites are often challenged to maintain their legacy SMF reporting as evolving technologies are implemented. IBM’s z Enterprise Data Compression (zEDC) hardware compression has been around since 2013, yet the most recent z15 processor advances included the Nest Accelerator Unit (NXU).
Advancements similar to the NXU are likely to become more commonplace since raw processor speeds have plateaued. Specialized processing drives new metrics to manage an already complex system. What’s affected? How will you keep up?
The on-chip z15 and future of processor hardware compression is transparent for existing applications that leverage zEDC (PCI-express) features on z14 and earlier. However, without proper visibility and management, these benefits can be lost or underappreciated as you deploy z15’s and beyond.
Effectively tracking compression demand whether using PCI express on pre-z15 processors or with the z15 on-chip nest accelerator (NXU) improves visibility of application performance and helps maintain configurations that will meet the demand. In this blog, I’ll review some important aspects of zEDC and how you can manage infrastructure, and exploit compression across processor generations.
z15 On Board Compression
The baseline benefits of zEDC include:
- Reduce disk storage requirements and I/O elapsed times
- Reduce bandwidth requirements and transfer times
- Often improve job elapsed time, and reduce CPU cycles
- Relatively straightforward and inexpensive to implement
- Can be leveraged by numerous widely used access methods and products
- Minimal CPU cost since more processing is offloaded from GCP work to the hardware
NXU offers additional benefits on top of these, including:
- Removes 15 LPAR limit for sharing compression imposed on the PCIe solution
- New concept of sharing and operating an accelerator function in the nest
- Support for DEFLATE compliant compression/decompression and GZIP CRC/ZLIB Adler
- Low latency
- High bandwidth
- Problem state execution (synchronous processing)
- Hardware/Firmware interlocks to ensure system responsiveness
- Architected instruction Executed in millicode
In addition, some of the z15 changes in compression are outlined below.
- Supported Software
IBM’s move off the compression functionality from PCIe Express cards in I/O drawers to the on-chip NXU allows for order of magnitude increases in compression throughput.
As Figure 1 below shows, transitioning to z15 also relaxes software requirements for exploiting compression, which gives customers more opportunities to exploit the increased throughput inherent with the z15 design.
IBM documentation is easily accessible and outlines more details regarding the differences between z14 and z15 compression including software feature requirements. Here are three good references to start with: zEDC White Paper, z/OS Integrated Accelerator (zEDC) and IBM z15 (8561) Technical Guide provide many details including the minimal migration considerations.
This hardware change is also accompanied by changes in the measurement data. Instead of generating data captured in RMF 74.9 records, legacy (asynchronous) compression operations (e.g., SMF Logstream and QSAM) create data in RMF 74.10 (EADM – Extended Asynchronous Data Mover) and 78.3 (IOP – I/O Processor) records. For synchronous operations, some CPU-level data is available through SMF 113 counters, but other metrics such as compression ratios are no longer available.
Visibility into zEDC Usage
The numerous benefits of these hardware solutions escape notice without an easy and practical way to navigate and monitor the data.
IntelliMagic Vision provides a comprehensive set of reports, including compression ratios, service and queue times, and request rates and throughput.
Figure 2 shows an example of IntelliMagic Vision’s easy compare feature of the compression ratio for zEDC Compress Requests.
Highly flexible drill-down capabilities of IntelliMagic Vision enable data to be viewed at the processor, system, card, or address space level. Migration activity can be easily evaluated by applying conditional filters and other specific customizations. A set of reports can be saved and shared on a custom dashboard.
Where possible, limitations in throughput and capabilities are exposed through thresholds and ratings to help focus analyst time spent on true ‘hot spots’ rather than manually reviewing 1000’s of metrics for 10’s of thousands of jobs and address spaces.
z15 Decompress/Compress Reporting (New Metrics)
As referenced above, the technology for compression changes, but there not many changes required to exploit the capability with new users of it. Asynchronous and Synchronous execution of decompress/compress activity generate different measures. The z15 instrumentation includes some new metrics included in the SMF 113 counters.
A group of thumbnail reports are shown below in Figure 3 and they include call rates, CPU cycles per call, and CPU wait metrics. These will help you ensure that the new on-chip technology performance is providing the throughput and benefits outlined above.
IntelliMagic Vision reports on these metrics related to the on-chip NXU that executes synchronous compression operations. These can be used to evaluate the effectiveness and usage of the new technology. A list of these reports is provided here:
- Extended Asynchronous Data Mover (EADM Overview)
- SSCH Rate to all SCM devices
- Decompression Rate to SCM devices
- Decompression Ratio to SCM devices
- Input Throughput for Decompression
- Output Throughput for Decompression
- Compression Rate to SCM devices
- Compression Ratio to SCM devices
- Input Throughput for Compression
- Output Throughput for Compression
Figure 4 below is an example of the “NXU Synchronous Call Deflate Activity Overview” report. These will initially be reported at the CPC level with drilldowns including by System.
IOP Resources Tracked as z15 Employs Them
IOP usage is well covered with a number of automatically rated reports in IntelliMagic Vision. Since the IOPs are exploited for asynchronous z15 compression/decompression activity, an additional report included.
Address Space Level Compress/Decompress Activity
zEDC activity at an address space level can help identify differences in activity that may lead to new insights as conversions to compressed data are implemented. z15 address space level activity is only for asynchronous execution of compression/decompression. The z14 reporting will continue to support your management of the activity as you transition from your current state to exploiting IBM’s latest offerings.
Efficient Preparation & Evaluation
Rather than spending precious hours:
- keeping up with new z15 measurement data
- identifying the correct fields to report on
- setting up reporting for new technology
- researching reasonable operational limits
Spend your time on a little background research and leverage the automated analysis of key metrics so that you can make efficient and actionable insights. IntelliMagic Vision can automatically highlight these for you and we would welcome an invite from you to improve your journey to the next level of IBM technology enhancements.
This article's author
Senior Consultant - z/OS
More from Jack
Share this blog
Start a Free Trial of IntelliMagic Vision for z/OS
Modernize your approach to mainframe performance management by moving away from static reports towards interactive, context-driven analytics for your end-to-end z/OS infrastructure.
IntelliMagic Vision Adds SMF Field Name Mapping to Live Report Editor
February 27, 2023 | IntelliMagic Vision version 12.1 provides the capability to easily reference and add variables by SMF field names.
A Performance Analyst’s Guide to Mainframe zERT Analysis | IntelliMagic zAcademy
This webinar recording will show real use-cases to introduce you to some of the ways to identify security risks and issues within network traffic.
Translating Application Performance Data into Business Outcomes on z/OS | IntelliMagic zAcademy
In this webinar, we explore practical steps for identifying and prioritizing your business-critical applications, and how to protect and report on their performance.