Upload
gerry-borja
View
47
Download
4
Tags:
Embed Size (px)
Citation preview
23/06/2003 Benchmark Methodology 1
WLM z/OS v1r4
ATS-PSSC MontpellierPascal Tillard
23/06/2003 / TP WLM & WAS 2
With WLM the service level administrator defines performance goals and assign a business importance to each goal. Goals are defined for work in business terms, and the system decides how much resource, such as CPU and storage, should be given to the work to meet its goal.Requires a shift of focus "from tuning at system resources level" "to defining performance expectations"
Workload Management
23/06/2003 / TP WLM & WAS 3
Workload ManagementPerformance Goals
Indicate the service level you would like to have for a given unit of work. There are three kinds of Goals:
VelocityResponse Time Discretionary
23/06/2003 / TP WLM & WAS 4
Workload ManagementService Class
A group of work with similar performance goals, business importance and resource requirements for management and reporting purposes
Workload Aggregated set of Service Classes for reporting purposes
Reporting ClassAggregate set of work for reporting purposes
23/06/2003 / TP WLM & WAS 5
Workload ManagementResource Group
Processor capacity boundary across the sysplex. Assigns minimum and maximum amount of CPUservice units / sec to work by assigning a Service Class to a Resource Group
Classification Rules - Classification GroupsAssign incoming work to a Service Class and Report ClassEach Work Manager (ex. JES) has its own Classification definition
23/06/2003 / TP WLM & WAS 6
Workload ManagementResource Group
Processor capacity boundary across the sysplex. Assigns minimum and maximum amount of CPUservice units / sec to work by assigning a Service Class to a Resource Group
Classification Rules - Classification GroupsAssign incoming work to a Service Class and Report ClassEach Work Manager (ex. JES) has its own Classification definition
23/06/2003 / TP WLM & WAS 7
WORKLOAD
Service Classes
ReportClass
ClassificationRules &Groups
Pd Goal impPd Goal imp
BATCH
Pd Goal imp
ResourceGroup
CB
BATCH
JESSubsystem
CB
TRANSACTIONS
JES
CICSIMSTSODB2DDFASCHOMVS
Subsystem
Service Classes
IWEBLSFM
CB
page 8
CB
23/06/2003 / TP WLM & WAS 8
Workload Management Services
Work Manager ServicesExecution Delay Monitoring ServicesEnclave ServicesQueuing Manager ServicesRouting Manager ServicesSysplex Routing ServicesScheduling Environment Services
AS
WAS
WAS5
WAS
WAS
WAS
23/06/2003 / TP WLM & WAS 9
Work Manager ServicesWork Manager Services allow WLM to:
Recognize a Subsystem Work Manager and the transactions it processes (IWMCONN - IWMDISC)Associate incoming work with a Service Class and optionally with a Report Class (IWMCLSFY) Recognize the address spaces that are processing the transactions
23/06/2003 / TP WLM & WAS 10
Enclave and Application EnvironmentFunctionalities that improve z/OS server capability
Enclave Services that allow management of a transaction across multiple address spaces and systems in a sysplexApplication Environment that gives the ability to WLM to start additional server address spaces to meet the goals.
Application Environment are exploited by Work Managers using Queing and Routing Manager WLM services
23/06/2003 / TP WLM & WAS 11
Enclave ServicesAn Enclave is an z/OS construct serving as:
unit of priority accounting for arriving transactions
Can spread across multiple dispatchable units and multiple address spacesAny number of Tasks and SRBs (preemptable) can be grouped together in an enclaveBusiness objectives (goals) are derived from enclave associated service class, not from the server(s) service class where the enclave dispatchable units are executedThree Enclave types: Independent, Dependent, Foreign
23/06/2003 / TP WLM & WAS 12
Enclave Resource AccountingEnclave type Independent Dependent Foreign
Disp. Unit SRBs / TCBs SRBs / TCBs SRBs / TCBs
New Tran. yes no no
Owner home a.s. iwmecrea home a.s. iwmecrea original enclave
Srv.CLs. or Pgn work mngr. cls. rules owner owner
CPU service (preemtible time)(enclave tcb/srb)
smf30 ownersm72 enclave s.c.
smf30 ownersmf72 owner s.c.
smf30 origin. owner smf 97 exec. syssmf72 enclave s.c.excuting system(s)
SRB service(non-preemtible time)
n/a n/a n/a
MSO service n/a smf30 ownersmf72 owner
n/a
IOC service smf30 & smf72 server(s) a.s.
smf30 & smf72server(s) a.s.
smf30 & smf72server(s) a.s.
23/06/2003 / TP WLM & WAS 13
Queuing Manager ServicesSubsystems using Queuing Managers services are logically divided in two major components:
Queuing Manager that receives transactions Server(s) that processes the transactions
The Queuing Manager:receives work requests queues to WLM for the execution in server address spaces.
WLM dynamically starts and maintains server address spaces as required to meet the work manager's goals.Queuing Manager services:
use WLM Application Environmentrequire a work manager to use Enclaveshave a system scope
23/06/2003 / TP WLM & WAS 14
Queuing Manager - Server example
Initialize subsystem and establish it as a queue manager Transaction starts
Accept workCreate Enclave
Queue Work Request
Remove Subsystem and terminate
Queuing Manager ASIWMCONNqueue_manager = YES
IWMCLSFYIWMECREAIWMQINSw/ Enclave Token
Initialize and Connect to application environment
Select Work from queue
Process Request
CompleteDelete Enclave
Transaction Ends
Told to terminateclean up, disconnect from application environment
terminate
work queues
Application EnvironmentApplication EnvironmentApplication Environment
SC A SC B
WLM AS Server Manager AS
IWMCONNserver_manager = YES
start
IWMSSEL
IWMSTBGN
IWMSTENDIWMEDELE
IWMSSELRC=0C
IWMDISC
IWMDISC
23/06/2003 / TP WLM & WAS 15
Application EnvironmentsServer A.S. management function is implemented through the Application Environment conceptA.E. is a grouping of transactions belonging to a Work Manager that use the same application librariesA.E.s can have System or Sysplex scope
Work Managers using WLM Queuing services have System scope (ex: WebSphere, DB2 Stored Procedure)Work Managers using WLM Routing services have Sysplex scope (ex: SOM)
A.E.s are defined using WLM policy Incoming requests should be assigned to an A.E. by the Work Manager and queued to WLMWLM manages Server A.S. (start/stop)
23/06/2003 / TP WLM & WAS 16
WLM-Managed Initiators - Review
Individual batch queues can be WLMmanagedInitiators are dynamically started by WLM tomeet service class period goals by reductionof batch queue delays and to optimizeresource usage WLM selects the system based on
Available system resourcesAvailability of waiting batch jobsImportance of the service class
Initiators are dynamically stopped by WLMWhen significantly more initiators exist thanneeded (> 1.5 times avg. queue length)In case of CPU or memory shortageAfter one hour of inactivity
23/06/2003 / TP WLM & WAS 17
Limitations Before z/OS V1R4
Balancing only when new initiators are Started
When initiators are already available, they will be used
New jobs can be started on any system where idle initiators are, regardless of system load
Often tends to batch jobs selected on heavilyloaded systems, while other systems in thesysplex have relaxed capacity available
Hurts discretionary workload on loaded systems
23/06/2003 / TP WLM & WAS 18
Enhanced Batch Initiator BalancingBalance distribution of initiators over sysplexmembers
More aggressive reduction of initiators onheavily loaded systems (< 5% CPU capacity)when other systems have enough idlecapacity
Start of new initiators on systems withrelaxed capacity (up to 5 initiators at once)
Balancing evaluation done every 10 seconds
WLM keeps enough initiators available forjobs with system affinity to constrainedsystems
23/06/2003 / TP WLM & WAS 19
WAS / WLM Interaction
2
1
3
4
6
5
W ebSphere ApplicationServer Instance
IIOPIIOP
CR
HTTPHTTP
SR1SR1
SC=CB01SC=CB01
1
SR2SR2
SC=IW EB01SC=IW EB01
2
SR3SR3
SC=CB02SC=CB02
3
SR4SR4
SC=CB03SC=CB03
4
SR5SR5
SC=CB04SC=CB04
5
SR6SR6
SC=CB05SC=CB05
6
MIN_SRS=1MAX_SRS>=6
6 Service Classes:
23/06/2003 / TP WLM & WAS 20
WLM - Classifying WebSphere Address Spaces
Daemon, Naming, SMS, Application Control Regions
Classify as SYSSTC or high velocity
Application Server regionsClassify with velocity goal, high enough to get started
Work is actually classified under the application environment
Garbage Collection runs under this service class.Don't make it too high because GC is CPU & storage-intensive
23/06/2003 / TP WLM & WAS 21
WLM - Classifying WebSphere Address Spaces
• Sample STC Classification rules: (use Report Classes!)
Qualifier Qualifier Starting Service Report # type name position Class Class - ---------- -------------- --------- -------- --------1 TN WSLDAP OPS_HI RWSLDAP 1 TN WSAPP1C OPS_HI RWSAPP1C 1 TN WSAPP1S OPS_MED RWSAPP1S 1 TN WS%%%%C OPS_HI RWSCTLRG 1 TN WS%%%%S OPS_MED RWSSVRRG
• OPS_HI service class: Importance= 1, Velocity = 70
• OPS_MED service class: Importance= 2, Velocity = 40
23/06/2003 / TP WLM & WAS 22
WLM - Classifying WebSphere Transactions
Subsystem type = CB using the following criteria:Server name (CN)Server instance name (SI) - not useful because instances share workUserid assigned to the transaction (UI) - not useful unless RUNAS=USERTransaction class (TC) - assigned from env. vars or a "URI mapping file":
BBOC_HTTP_TRANSACTION_CLASS= (default for server or SI)BBOC_HTTP_SSL_TRANSACTION_CLASS= (same if coming in via SSL) BBOC_HTTPALL_TCLASS_FILE= (points to HFS file - see next foil)
Percentage response time goal is recommendedEx. 80% of trans less than 0.5 seconds (or high velocity default SC)Default is SYSOTHER ("scum")
23/06/2003 / TP WLM & WAS 23
Classification by Virtual host, Port, or URIQualifier Qualifier Start Service Report # type name position Class Class - --------- -------- -------- -------- --------
Default: CBMED RCBDEFLT1 CN WSPROD 1 CBMED RWSPROD2 . TC . TCLASS1 CBFAST RWSPRD12 . TC . TCLASS2 CBMED RWSPRD21 CN WSTEST 1 CBSLOW RTSTEST 2 . UI . USER1 CBMED RTSTSTU22 . TC . TCLASS5 CBSLOW RTSTST5
Transaction Class Mapping file format:TransClassMap <host>:<port> <uritemplate> <tclass>TransClassMap www.ibm.com:80 /Webap1/myservlet TCLASS1TransClassMap www.ibm.com:* /Webap1/myservlet TCLASS2TransClassMap *:443 * TCLASS3TransClassMap *:* /Webap1/myservlet TCLASS4TransClassMap * * TCLASS5
Examples:ibm.com:80/Webap1/myservlet => TCLASS1 => CBFAST (RWSPRD1)ibm.com:443/Webap1/xservlet => TCLASS2 => CBMED (RWSPRD2)
23/06/2003 / TP WLM & WAS 24
Monitor IREPORT CLASS=RWASPAS DESCRIPTION =WAS Controller Region
TRANSACTIONS TRANS.-TIME SS.TTT --SERVICE RATES-- PAGE-IN RATES ----STORAGE----AVG 1.00 ACTUAL 0 ABSRPTN 117 SINGLE 0.0 AVG 4588.00MPL 1.00 EXECUTION 0 TRX SERV 117 BLOCK 0.0 TOTAL 4587.99ENDED 0 QUEUED 0 TCB 4.7 SHARED 0.0 CENTRAL 4535.99END/S 0.00 R/S AFFINITY 0 SRB 0.4 HSP 0.0 EXPAND 52.00#SWAPS 0 INELIGIBLE 0 RCT 0.0 HSP MISS 0.0EXCTD 0 CONVERSION 0 IIT 0.0 EXP SNGL 0.0 SHARED 0.00AVG ENC 0.00 STD DEV 0 HST 0.0 EXP BLK 0.0REM ENC 0.00 APPL % 1.7 EXP SHR 0.0MS ENC 0.00
REPORT CLASS=RWASPASS DESCRIPTION =WAS Server Region
TRANSACTIONS TRANS.-TIME SS.TTT --SERVICE RATES-- PAGE-IN RATES ----STORAGE----AVG 2.00 ACTUAL 0 ABSRPTN 333 SINGLE 0.0 AVG 85878.1MPL 2.00 EXECUTION 0 TRX SERV 333 BLOCK 0.0 TOTAL 171756ENDED 0 QUEUED 0 TCB 2.6 SHARED 0.0 CENTRAL 171756END/S 0.00 R/S AFFINITY 0 SRB 0.0 HSP 0.0 EXPAND 0.00#SWAPS 0 INELIGIBLE 0 RCT 0.0 HSP MISS 0.0EXCTD 0 CONVERSION 0 IIT 0.0 EXP SNGL 0.0 SHARED 4365.99AVG ENC 0.00 STD DEV 0 HST 0.0 EXP BLK 0.0REM ENC 0.00 APPL % 0.9 EXP SHR 0.0MS ENC 0.00
REPORT CLASS=RWASWEB DESCRIPTION =Report WAS TCWASPAS Enclave
TRANSACTIONS TRANS.-TIME SS.TTT --SERVICE RATES-- PAGE-IN RATES ----STORAGE----AVG 0.21 ACTUAL 12 ABSRPTN 1292 SINGLE 0.0 AVG 0.00MPL 0.21 EXECUTION 12 TRX SERV 1292 BLOCK 0.0 TOTAL 0.00ENDED 4974 QUEUED 0 TCB 11.9 SHARED 0.0 CENTRAL 0.00END/S 16.58 R/S AFFINITY 0 SRB 0.0 HSP 0.0 EXPAND 0.00#SWAPS 0 INELIGIBLE 0 RCT 0.0 HSP MISS 0.0EXCTD 0 CONVERSION 0 IIT 0.0 EXP SNGL 0.0 SHARED 0.00AVG ENC 0.21 STD DEV 12 HST 0.0 EXP BLK 0.0REM ENC 0.00 APPL % 4.0 EXP SHR 0.0MS ENC 0.00
23/06/2003 / TP WLM & WAS 25
Little’s Law
λ: customer arrival rateN: average number of customers in systemT: average delay per customer in systemLittle’s Theorem: System in steady-state
N Tλ=
N
T
λ
Lq = W
23/06/2003 / TP WLM & WAS 26
ProofArrival Threads Ended/sec Time/tx TCB time Waiting MPL Appl%rate tx/s number millisec /tx ms Time ms
100 1 99,36 7 2,8 4,2 0,7 28100 3 99,43 6,8 2,7 4,1 0,68 27,6200 3 199,33 7,4 2,8 4,6 1,48 55,3300 3 299,38 9,1 2,8 6,3 2,73 85,9400 3 396,29 17,2 2,7 14,5 6,82 109,3400 6 399,66 8,7 2,8 5,9 3,48 112,1500 10 499,36 11,4 2,8 8,6 5,7 142,2600 10 598,45 30 2,9 27,1 17,99 176,3700 10 696,79 40,6 2,8 37,8 28,31 200,9
Little's Law
0
50
tx/sec051015202530
resp.time ms MPL
resp.time ms 6,8 7,4 9,1 17,2 11,4 30 40,6
MPL 0,68 1,48 2,73 6,82 5,7 17,99 28,31
100 200 300 400 500 600 700
23/06/2003 / TP WLM & WAS 27
Enclave report limitationProblem
Currently no possibility exists to report more than the response time for enclaves for subsystems/applications creating enclaves for transaction performance management.
Subsystems like CICS and IMS have the ability to create monitoring environments and present subsystem states for reporting and analysis purposes.
23/06/2003 / TP WLM & WAS 28
SolutionExternal interfaces for monitoring environments have been changed to allow WLM to establish report-only performance blocks (PBs)
External interfaces have been changed to enable association of report-only PBs with enclaves and address spaces
Extended sampling for report-only performance blocks
Collect data for other goal types than just response time goals
Include states for multi-period service classes
ExploiterWebsphere Application Server for z/OS (in a new WAS release)WLM support in R4, PTFs rolled back to R2 & R3
23/06/2003 / TP WLM & WAS 29
Execution Delay Monitoring Services
Allow WLM to know how well the work is executed and where delays are occurring Only response time goals can be used WLM does not individually manage transactions resource utilizationWLM can allocate resources to address spaces based on the behavior of the transactions being executed by themUsed by CICS , IMS and WAS v5
23/06/2003 / TP WLM & WAS 30
ExternalsIWMMCREA - Create Delay Monitoring Environment - changedIWMMDELE - Delete Delay Monitoring Environment IWMMINIT - Initialize Delay Monitoring Environment - changedIWMMRELA - Relate Delay Monitoring Environment - changedIWMMCHST - Change State of Work unit (inline only) - changedIWMMXFER - Monitoring Environment Transfer (inline only) IWMMSWCH - Monitoring Environment Switch IWMMNTFY - Notify of work execution completion - changedIWMRPT - Report Response Time - changed IWMMEXTR - Monitoring Environment Extract Service - changedIWMMABNL - Monitor Environment Abnormal Event Service (inline only) IWMMREG - Resource monitoring registration IWMMDREG - Resource monitoring deregistration
23/06/2003 / TP WLM & WAS 31
Z/OS Worload Simulator Architecture
config files
z/OS Engine
WorkloadSimulatorDaemon
Windows Controller
target application
Host AIX - WIN - z/OS - Linux
Http Server
WebSphere AS
GUI applicationCapture Play backAnalyse
Http log
trace file
Http error
xml report
WebMonitor
Performance agent
BrowserStop simulation Start simulationMonitor run
http/https
ftp
23/06/2003 / TP WLM & WAS 32
RMF Mon III: Response Time distribution