Shmuel,
I remember spending some time playing with CPU affinity trying to
keep the CPU bound jobs away from the AP
Why?
[Ron Hawkins] Nice catch. I meant to say IO Bound Jobs.
Ron
--
For IBM-MAIN subscribe / signoff /
In 005a01cbff6c$b63dded0$22b99c70$@hawkins1...@sbcglobal.net, on
04/20/2011
at 08:07 AM, Ron Hawkins ron.hawkins1...@sbcglobal.net said:
I remember spending some time playing with CPU affinity trying to
keep the CPU bound jobs away from the AP
Why?
Someone correct me please, but didn't it
vs AP: Was CPU
utilization/forecasting
http://www.garlic.com/~lynn/2011f.html#50 Dyadic vs AP: Was CPU
utilization/forecasting
360370 had two-processor multiprocessor shared memory and although had
dedicated channels ... tended to try and simulate shared channels by
trying to configure the same
Ron, care to remind us of the modelling difference? It's been a while. :-)
Ron Hawkins wrote:
Would it have been more appropriate if I added that dyadic
processors required revision of many of the methods that
we applied to earlier models.
Would you use a capacity planning methodology
martin_pac...@uk.ibm.com (Martin Packer) writes:
Ron, care to remind us of the modelling difference? It's been a while. :-)
360 370 dual-processors shared memory but each processors had its own
dedicated channels ... and the configuration could be split and run as
two separate processors.
Martin,
Yeah, what he said :-)
Ron
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of
Anne Lynn Wheeler
Sent: Wednesday, April 20, 2011 7:05 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: [IBM-MAIN] Dyadic vs AP: Was CPU utilization
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of
Martin Packer
Sent: Wednesday, April 20, 2011 3:14 AM
To: IBM-MAIN@bama.ua.edu
Subject: [IBM-MAIN] Dyadic vs AP: Was CPU utilization/forecasting
Ron, care to remind us
and the 3081 which couldn't be
split). 3081 had both processors being able to address all channels and
also introducted 31-bit virtual addressing.
re:
http://www.garlic.com/~lynn/2011f.html#41 CPU utilization/forcasting
http://www.garlic.com/~lynn/2011f.html#49 Dyadic vs AP: Was CPU
utilization
Interesting - especially the CSA bit: The very first problem I worked on
in IBM (and I don't think I was much use) :-) in late 1985 was Virtual
Storage (a DOS to MVS migration). I was hooked. If I hadn't've been I'd
not've ;lasted long in IBM and the world would've been a different place.
:-)
Ron,
We had the same DUO issue (we had an mp) . One of the sysprogs had to write a
program that cleared out DUO
Area in low memory(yech). Duo was one of the poorer written utilities (not a
good term) that didn#39;t transfer well from Mvt to MVS.
Ed
10 matches
Mail list logo
