Hw & SW New Functions

Transcription

1 Hw & SW New Functions Discussion Milano, 8 Novembre 2016 Roma, 10 Novembre 2016 Marita Prassolo Distinguished Engineer IBM Italy Analyt ic s Mobile Cloud Securit y Social Semiconductor Technology Microprocessor Design Systems Design Virtualization & Operating Systems Compilers, Tools & Java Virtual Machine Optimized Middleware

2 Agenda Øz13 internal design Ø z/os current support ØFeatures and software support: Ø discussion! ØWLM: a key player between hardware and software 2016 IBM Corporation Page 2

3 Base z13 support New limits for z13 85 LPARs Up to 141 processors per CPC Up to 141-way on z/os V2.1 (non-smt mode) Up to 128-way on z/os V2.1 (SMT mode), or z/os <V2.1 Maximum active threads in SMT mode is 213 with ziip:cp ratio of 2:1 New Cache topology Chip, node, drawer No longer using books z/os HiperDispatch uses new topology information to place work topologically close to maximize cache efficiency 2016 IBM Corporation Page 3

4 z13 CPC Drawer Cache Hierarchy Detail Single CPC Drawer View (N30 Model) 2 Nodes 2 SC SCM Chips (1 per node) Node 1 Node 2 SC SCM1 NIC Memory L4 Cache NIC Memory L4 Cache SC SCM2 6 PU SCM Chips (3 per node) L3 Cache L3 Cache L3 Cache L3 Cache L3 Cache L3 Cache L1 L1 L1 L1 L1 L1 PU1 PU8 PU1 PU8 PU1 PU8 PU SCM1 PU SCM2 PU SCM3 L1 L1 L1 L1 L1 L1 PU1 PU8 PU1 PU8 PU1 PU8 PU SCM4 PU SCM5 PU SCM6 * Up to 8 PU cores per chip Node 1 - Caches L1 private 96k i, 128k d private 2 MB i + 2 MB d L3 shared 64 MB / chip L4 shared 480 MB / node - plus 224 MB NIC Node 2 - Caches L1 private 96k i, 128k d private 2 MB i + 2 MB d L3 shared 64 MB / chip L4 shared 480 MB / node - plus 224 MB NIC Single PU core * Not all PU s active IBM Corporation Page 4

5 WLM Topology Report Tool (As-is) Sample output (z13): New as-is tool available for download from the WLM homepage res/wlm/wlm_further_info_tools.html#to pology Visualizes mapping of HiperDispatch affinity nodes to physical structure Supports IBM zec10 and later To use: 1. Download from above location 2. Run installer 3. Collect SMF99.14 records 4. Upload Host code to a z/os system Sample output (zec12): IBM Corporation Page 5

6 z/os and support Service: With z/os V2, IBM plans to provide 5 years of z/os support, with 3 years of optional fee-based extended service z/os V1policy is 3 years of support with a 2 year optional fee-based extended service Support: z/os V2.1 is supported through 9/2018 to allow customers appropriate time to deploy new functions z/os V1.13 is now supported through 9/ Year Support 1 Yr Support 3Yrs Service 3 YearsSupport 2 Yrs Support 3 Yrs Service 5 Years Support 3 Yrs Service 5 Years Support 3 Yrs Service 5 Years Support *Chart represents current IBM plans and are subject to change 2016 IBM Corporation Page 6

7 Features and software support Feature description Available on Use Cases Pre-reqs SMT on ziip z13, z13s All ziip eligible workload z/os 2.1 or + SMT on IFL z13, z13s All IFL eligible workload z/vm 6.3 or + and Linux SIMD z13, z13s CPLEX, Cognos, Cobol, PL1, ASM, z/os 2.1 or + Large Pages (1MB) z10ec and beyond DB2 buffer pools, WAS heap size, MQ Large Pages (2 GB) z196 and beyond DB2 buffer pools, WAS heap size, MQ CMPSC all z Systems DB2 table spaces, SMS managed datasets SMC-D z13 GA2, z13s z/os 2.2 zhyperwrite z196 and beyond DB2 10 or 11, DS8K, PPRC OSA ICC - SSL/TLS z13 GA2, z13s SSL/TLS support on OSA ICC (Type OSC) IBM zaware zec12, zbc12 and beyond CPACF all z Systems Crypto Express 5S z13, z13s Crypto Express 4S zec12, zbc12 zedc zec12, zbc12 and beyond SMF, BSAM/QSAM, z/os 2.1 or +, zedc SW enablement Flash Express zec12, zbc12 and beyond SVC Dumps, MQ in CF, Paging activity RoCE zec12, zbc12 and beyond Sysplex distributor, FTP, z/os 2.1 or IBM Corporation Page 7

8 Motivation for Simultaneous Multi Threading Simultaneous multithreading (SMT) permits multiple independent threads of execution to better utilize the resources provided by modern processor architectures. * With z13, SMT allows up to two instructions streams per core to run simultaneously to get better overall throughput SMT is designed to make better use of processor hardware units On z/os, SMT is available for ziip processing: Two concurrent threads are available per core Capacity (throughput) usually increases Performance may be superior using single threading instructions Load/Store (L1 Cache) A B A Cache Shared Cache B A A B Use of Pipeline Stages in SMT Thread-A B A B A A A A / B B A A Both threads Execution Units (FXU/FPU) A A B B A B Thread-B Stage idle IBM Corporation Page 8

9 What is new with multithreading support? New support LOADxx: PROCVIEW CPU LOADxx: PROCVIEW CORE This the existing mode that you z/os is core-aware and maps CPUs to cores. are used to Core syntax for CPU/core related commands. IPL required z/os does only know processors (CPUs) MT1 Mode IEAOPTxx: MT_ZIIP_MODE = 1 SET OPT=yy IEAOPTxx: MT_ZIIP_MODE = 2 Possible on any supported hardware z13 only MT1 performance & capacity MT2 performance & cap. HiperDispatch=No possible 9 MT2 Mode HiperDispatch=Yes enforced (on z13) 2016 IBM Corporation Page 9

10 IBM Presentation Template Full Version z/os MT Capacity Factors - used by WLM/SRM Capacity Factor (CF) How much work core actually completes for a given workload mix at current utilization - relative to single thread Therefore, MT1 Capacity Factor is 1.0 (100%) MT2 Capacity Factor is workload dependent Describes the actual, current efficiency of MT2 Maximum Capacity Factor (mcf) How much work a core can complete for a given workload mix at most relative to MT-1 mode Used to estimate MT2 efficiency if the system was fully utilized E.g., to derive WLM view of total system capacity or free capacity Value range of CF and mcf is [ ] Expect CF in a range of (100%-140%) for typical workloads Untypical ( pathological ) workloads may see untypical/pathological CF/mCFs, such as < IBM Corporation Page 10

11 Transitioning into MT2 mode: WLM considerations Less overflow from ziip to CPs may occur because ziip capacity increases, and number of ziip CPUs double CPU time and CPU service variability may increase, because Threads which are running on a core at the same time influence each other Threads may be dispatched at TD1 or TD2 Unlike other OS, z/os attempts to dispatch threads densely Sysplex workload routing: routing recommendation may change because ziip capacity will be adjusted with the mcf to reflect MT2 capacity mcf may change as workload or workload mix changes Goals should be verified for ziip-intensive work, because The number of ziip CPUs double and the achieved velocity may change Chatty (frequent dispatches) workloads may profit because there is a chance of more timely dispatching More capacity is available Any single thread will effectively run at a reduced speed and the achieved velocity will be lower. Affects processor speed bound work, such as single threaded Java batch MT-2 APPL% numbers can continue to be used to understand relative core utilization in a given interval, at times of comparable maxcfs. However, the maxcf needs to be considered when comparing APPL% across different workloads or times with different maxcf values IBM Corporation Page 11

12 Two new capping options Function z/os release V2.2 V2.1 z13 GA2 LPAR Absolute group capping OA47752 OA47752 Absolute MSU capping OA49201 OA49201 LPAR absolute group capping Feature of PR/SM as of z13 GA2, and z13s Like LPAR absolute capping but for a group of LPARs Specified on the HMC as number of processors with 2 decimal places (like 3.75). All processor classes supported. Recognized by WLM as possible limit to the LPAR capacity Absolute MSU capping Function of WLM provided by APAR OA49201 Similar to WLM defined capacity or group capacity but LPAR will always be capped Independent of 4 hour rolling average consumption. General purpose processor Specified in IEAOPTxx. Limit is the LPAR defined capacity or group capacity specified on the HMC in MSU IBM Corporation Page 12

13 Using absolute MSU capping IEAOPTxx ABSMSUCAPPING= NO YES AbsMSUcapping=Yes limits LPAR consumption to a certain MSU number at all times. I.e., the system loses the flexibility of consuming above the defined capacity limit while the four hour rolling average is below the limit. Limit remains stable even when CEC configuration changes, e.g. through On/Off CoD or CBU activations or deactivations. Absolute MSU capping is an effective means to permanently limit the consumption of an LPAR to a specific MSU figure at all times (including times when the four-hour rolling average does not exceed the defined limit.) Defined capacity limits and group capacity limits should be enforced only while the long term four hour rolling average consumption exceeds the respective limit (existing and usually desired behavior). Defined capacity limits and group capacity limit should be enforced permanently, independently of the long term four hour rolling average consumption. When used with an LPAR capacity group: Limit on behalf of the group entitlement will always be enforced Regardless of the four-hour rolling group average consumption. All members of a capacity group that use AbsMSUcapping=YES will permanently enforce the limit on behalf of the capacity group. All members of a capacity group that do not use AbsMSUcapping=YES will be capped while the group four-hour rolling group average consumption is greater or equal to the group limit 2016 IBM Corporation Page 13

14 Comparison of capping 2016 IBM Corporation Page 14

15 Which capping techniques may be combined? (1) Includes ABSMSUCAPPING=NO and ABSMSUCAPPING=YES 2016 IBM Corporation Page 15

16 Reporting enhancements for CICS and IMS, and Mobile Workloads Mobile Workload Pricing (MWP) is an IBM Software Pricing option, announced in May For eligible software it can reduce the cost of transactions that originate on mobile devices. MWP can mitigate the impact of mobile workloads on sub-capacity license charges, specifically in the cases where higher mobile transaction volumes may cause a spike in machine utilization. Reporting enhancements for CICS and IMS, and Mobile Workloads introduce WLM enhancements that can simplify the identifying and reporting of the mobile-sourced transactions and their processor consumption. WLM introduces a new transaction level attribute in the WLM classification rules that allows for the identification of mobile transactions and the reporting of their processor consumption. With exploiting levels of CICS and IMS, processor consumption data are made available on the transaction service and report classes including such transactions IBM Corporation Page 16

17 Enablement of Reporting Enhancements for Mobile Workloads * Statements regarding IBM future direction and intent are subject to change or withdrawal, and represent goals and objectives only IBM Corporation Page 17

18 WLM Support for Mobile Pricing In their WLM classification rules, installations can classify transactions as "mobile" The assigned mobile attribute is independent from the assigned service and report class ( Eliminates the need for using new dedicated classes for mobile workload reporting) The mobile attribute is transparent to subsystems WLM tracks and reports the total and the mobile CPU consumption for all service and report classes Eligible exploiters of the WLM Execution Delay Monitoring Services like CICS or IMS can provide CPU times for all their transactions As soon as they do, total and mobile CPU consumption data is also available for CICS and IMS transaction service and report classes that previously did not report any CPU consumption data Subsystems using independent enclaves can participate transparently; only the classification rules need to be updated. WLM also aggregates and reports the system-wide mobile consumption data 2016 IBM Corporation Page 18

19 WLM-managed DB2 Bufferpools: Overall flow Enclave Database Manager DB2 registers bufferpool with WLM WLM will recommend to grow the size of the bufferpool when the Performance Index of a Service Class Period is impacted and bufferpool delays are a significant contributor WLM will recommend to shrink the size of the bufferpool due to donation to a suffering Service Class period, or due to regular housekeeping cycles DB2 de-registers bufferpool from WLM management Program Application Task WLM gathering performance data to recognize whether a Buffer Pool size change is necessary Access Method BPMgmtOnly Performance Block Buffer Pool Performance Block Sampling WLM/SRM Data Collect Exit A. C. ALTER BUFFERPOOL [VPSIZE(s)] AUTOSIZE(YES) è MIN size = 0.75 x VPSIZE è MAX size = 1.25 x VPSIZE B. Buffer Pool Manager Adjust Algorithms Initial USED size between MIN size and MAX size Management range between MIN and MAX sizes Adjust Exit D. DASD 2016 IBM Corporation Page 19

20 WLM-Managed DB2 Bufferpool: Changes in z/os V2.2 plus V2.1 A bufferpoolcan be increased when Performance index impacted and buffer pool delays are a significant contributor A bufferpoolmay shrink Due to donation to a suffering service class period May suffer storage related delays Due to regular housekeeping cycles Consider one BP reduction candidate per 10 sec interval BP idle - had no references No delays, i.e. 100% hit ratio Least important period showing buffer pool delays Any bufferpool may shrink no more than once per 5 min Hit Ratio Historic observations Buffer Pool Size min max When WLM recommends to increase the size of a bufferpool, DB2 accepts the recommended size as new current VPSIZE. DB2 does not necessarily use the entire recommended size è Used size of the bufferpool will be less or equal the current VPSIZE 2016 IBM Corporation Page 20

21 WLM Support for I/O Priority Manager in DS8K Series WLM collaborates with the I/O Priority Manager in DS8700 & DS8800 storage servers (This feature is supported on IBM System Storage DS8700 and DS8800 series, and requires a DS8000 licensed machine code) WLM sends I/O Priority Manager information about the goal fulfillment and importance of z/os workloads (service classes). Passing these performance parameters to the storage server enables the I/O Priority Manager to determine which I/O requests are more important than others and which I/O requests need to be processed faster to fulfill the performance goals defined for the corresponding workload in z/os. Using the passed information from WLM, the I/O Priority Manager throttles I/O requests of workloads which exceed their goals to help I/O requests of workloads which do not fulfill their goals. IEAOPT parameter STORAGESERVERMGT={YES NO} 2016 IBM Corporation Page 21

22 Analyt ic s Mobile Cloud Securit y Social Semiconductor Technology Microprocessor Design Systems Design Virtualization & Operating Systems Compilers, Tools & Java Virtual Machine Optimized Middleware

23 Trademarks The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both. Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not actively marketed or is not significant within its relevant market. Those trademarks followed by are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States. For a complete list of IBM Trademarks, see *, AS/400, e business(logo), DBE, ESCO, eserver, FICON, IBM, IBM (logo), iseries, MVS, OS/390, pseries, RS/6000, S/30, VM/ESA, VSE/ESA, WebSphere, xseries, z/os, zseries, z/vm, System i, System i5, System p, System p5, System x, System z, System z9, BladeCenter The following are trademarks or registered trademarks of other companies. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunicati ons Agency, which is now part of the Office of Government Commerce. * All other products may be trademarks or registered trademarks of their respective companies. Notes: Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here. IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply. All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions. This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Information about non-ibm products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography IBM Corporation Page 23