How to identify processor manager req. for GS1280?

Clark Powell — Tue, 22 Dec 2009 16:13:05 GMT

We recently move our GE/Cache application from a 4 processor ES45 to an eight processor GS1280. I understand that at a certain point the number of processors will dictate that one processor be used exclusively for processor management for efficiency; I just don't know at what point that occurs. Could anybody give me some suggestions for deturmining this?

thanks
Clark Powell

below are the present processor stats.
ALPHAD>
ALPHAD> sho cpu/full

System: ALPHAD, hp AlphaServer GS1280 7/1150

SMP execlet = 3 : Enabled : Streamlined.
Config tree = Version 6
Primary CPU = 0
HWRPB CPUs = 64
Page Size = 8192
Revision Code =
Serial Number = AY40301579
Default CPU Capabilities:
System: QUORUM RUN
Default Process Capabilities:
System: QUORUM RUN

CPU 0 State: RUN CPUDB: 82452000 Handle: 00002680
Owner: 000007C0 Current: 000007C0 Partition 0 (ALPHAD)
ChgCnt: 13 State: Present, Primary
Process: * None *
Capabilities:
System: PRIMARY QUORUM RUN RAD0
Slot Context: 9899C180
CPU - State..........: RC, PA, PP, CV, PV, PMV, PL
Type...........: EV7 (21364), Minor = 5
Speed..........: 1150 Mhz
Variation......: VAX FP, IEEE FP, Primary Eligible
Serial Number..:
Revision.......:
Halt Request...: 0
Software Comp..: 0.0
PALCODE - Revision Code..: 2.11-01
Compatibility..: 25
Max Shared CPUs: 256
Memory Space..: Physical = 00000000.00000000 Length = 0
Scratch Space..: Physical = 00000000.00000000 Length = 0
Bindings:
NETACP PID = 22C00824 Reason: PRIMARY Capability
Fastpath: * None *
Features:
Autostart - Enabled.
Fastpath - Selection enabled as Preferred CPU.

CPU 1 State: RUN CPUDB: 8254F180 Handle: 00005200
Owner: 000007C0 Current: 000007C0 Partition 0 (ALPHAD)
ChgCnt: 13 State: Present, Reassignable
Process: * None *
Capabilities:
System: QUORUM RUN RAD0
Slot Context: 9899C400
CPU - State..........: RC, PA, PP, CV, PV, PMV, PL
Type...........: EV7 (21364), Minor = 5
Speed..........: 1150 Mhz
Variation......: VAX FP, IEEE FP, Primary Eligible
Serial Number..:
Revision.......:
Halt Request...: 0
Software Comp..: 0.0
PALCODE - Revision Code..: 2.11-01
Compatibility..: 25
Max Shared CPUs: 256
Memory Space..: Physical = 00000000.00000000 Length = 0
Scratch Space..: Physical = 00000000.00000000 Length = 0
Bindings: * None *
Fastpath:
PKA0
EIA0
EIB0
EWA0
FGA0
Features:
Autostart - Enabled.
Fastpath - Selection enabled as Preferred CPU.

CPU 2 State: RUN CPUDB: 82550180 Handle: 00007B80
Owner: 000007C0 Current: 000007C0 Partition 0 (ALPHAD)
ChgCnt: 13 State: Present, Reassignable
Process: * None *
Capabilities:
System: QUORUM RUN RAD0
Slot Context: 9899C680
CPU - State..........: RC, PA, PP, CV, PV, PMV, PL
Type...........: EV7 (21364), Minor = 5
Speed..........: 1150 Mhz
Variation......: VAX FP, IEEE FP, Primary Eligible
Serial Number..:
Revision.......:
Halt Request...: 0
Software Comp..: 0.0
PALCODE - Revision Code..: 2.11-01
Compatibility..: 25
Max Shared CPUs: 256
Memory Space..: Physical = 00000000.00000000 Length = 0
Scratch Space..: Physical = 00000000.00000000 Length = 0
Bindings: * None *
Fastpath:
PEA0
Features:
Autostart - Enabled.
Fastpath - Selection enabled as Preferred CPU.

CPU 3 State: RUN CPUDB: 82551180 Handle: 00009180
Owner: 000007C0 Current: 000007C0 Partition 0 (ALPHAD)
ChgCnt: 13 State: Present, Reassignable
Process: * None *
Capabilities:
System: QUORUM RUN RAD0
Slot Context: 9899C900
CPU - State..........: RC, PA, PP, CV, PV, PMV, PL
Type...........: EV7 (21364), Minor = 5
Speed..........: 1150 Mhz
Variation......: VAX FP, IEEE FP, Primary Eligible
Serial Number..:
Revision.......:
Halt Request...: 0
Software Comp..: 0.0
PALCODE - Revision Code..: 2.11-01
Compatibility..: 25
Max Shared CPUs: 256
Memory Space..: Physical = 00000000.00000000 Length = 0
Scratch Space..: Physical = 00000000.00000000 Length = 0
Bindings: * None *
Fastpath:
BG0
Features:
Autostart - Enabled.
Fastpath - Selection enabled as Preferred CPU.

CPU 4 State: RUN CPUDB: 82552180 Handle: 0000BB00
Owner: 000007C0 Current: 000007C0 Partition 0 (ALPHAD)
ChgCnt: 13 State: Present, Reassignable
Process: * None *
Capabilities:
System: QUORUM RUN RAD0
Slot Context: 9899CB80
CPU - State..........: RC, PA, PP, CV, PV, PMV, PL
Type...........: EV7 (21364), Minor = 5
Speed..........: 1150 Mhz
Variation......: VAX FP, IEEE FP, Primary Eligible
Serial Number..:
Revision.......:
Halt Request...: 0
Software Comp..: 0.0
PALCODE - Revision Code..: 2.11-01
Compatibility..: 25
Max Shared CPUs: 256
Memory Space..: Physical = 00000000.00000000 Length = 0
Scratch Space..: Physical = 00000000.00000000 Length = 0
Bindings: * None *
Fastpath:
EWB0
FGB0
Features:
Autostart - Enabled.
Fastpath - Selection enabled as Preferred CPU.

CPU 5 State: RUN CPUDB: 82553200 Handle: 0000D100
Owner: 000007C0 Current: 000007C0 Partition 0 (ALPHAD)
ChgCnt: 13 State: Present, Reassignable
Process: * None *
Capabilities:
System: QUORUM RUN RAD0
Slot Context: 9899CE00
CPU - State..........: RC, PA, PP, CV, PV, PMV, PL
Type...........: EV7 (21364), Minor = 5
Speed..........: 1150 Mhz
Variation......: VAX FP, IEEE FP, Primary Eligible
Serial Number..:
Revision.......:
Halt Request...: 0
Software Comp..: 0.0
PALCODE - Revision Code..: 2.11-01
Compatibility..: 25
Max Shared CPUs: 256
Memory Space..: Physical = 00000000.00000000 Length = 0
Scratch Space..: Physical = 00000000.00000000 Length = 0
Bindings: * None *
Fastpath:
PKB0
Features:
Autostart - Enabled.
Fastpath - Selection enabled as Preferred CPU.

CPU 6 State: RUN CPUDB: 82554200 Handle: 0000FA80
Owner: 000007C0 Current: 000007C0 Partition 0 (ALPHAD)
ChgCnt: 13 State: Present, Reassignable
Process: * None *
Capabilities:
System: QUORUM RUN RAD0
Slot Context: 9899D080
CPU - State..........: RC, PA, PP, CV, PV, PMV, PL
Type...........: EV7 (21364), Minor = 5
Speed..........: 1150 Mhz
Variation......: VAX FP, IEEE FP, Primary Eligible
Serial Number..:
Revision.......:
Halt Request...: 0
Software Comp..: 0.0
PALCODE - Revision Code..: 2.11-01
Compatibility..: 25
Max Shared CPUs: 256
Memory Space..: Physical = 00000000.00000000 Length = 0
Scratch Space..: Physical = 00000000.00000000 Length = 0
Bindings: * None *
Fastpath: * None *
Features:
Autostart - Enabled.
Fastpath - Selection enabled as Preferred CPU.

CPU 7 State: RUN CPUDB: 82555200 Handle: 00011080
Owner: 000007C0 Current: 000007C0 Partition 0 (ALPHAD)
ChgCnt: 13 State: Present, Reassignable
Process: UX2KSDRV_VMCROU PID: 22C009E6
Capabilities:
System: QUORUM RUN RAD0
Slot Context: 9899D300
CPU - State..........: RC, PA, PP, CV, PV, PMV, PL
Type...........: EV7 (21364), Minor = 5
Speed..........: 1150 Mhz
Variation......: VAX FP, IEEE FP, Primary Eligible
Serial Number..:
Revision.......:
Halt Request...: 0
Software Comp..: 0.0
PALCODE - Revision Code..: 2.11-01
Compatibility..: 25
Max Shared CPUs: 256
Memory Space..: Physical = 00000000.00000000 Length = 0
Scratch Space..: Physical = 00000000.00000000 Length = 0
Bindings: * None *
Fastpath: * None *
Features:
Autostart - Enabled.
Fastpath - Selection enabled as Preferred CPU.

Re: How to identify processor manager req. for GS1280?

Volker Halle — Tue, 22 Dec 2009 16:40:52 GMT

Clark,

OpenVMS itself does not use one processor for 'processor management'. Some functions can only be executed on the primary CPU (e.g. timekeeping), but everything else is distributed.

You could dedicate a certain CPU exclusively to the lock manager or TCPIP, but that's up to you.

Don't know about GE/cache - if your question was directed against this product.

Volker.

Re: How to identify processor manager req. for GS1280?

Andy Bustamante — Tue, 22 Dec 2009 17:52:40 GMT

As Volker points out, you may be thinking of the dedicated lock manager. This may or may not have an impact on your system's performance. Use $ MONITOR MODE and check "MP Synchronization" over time. T4 will also provide this data.

Another option is, try it. This is a dynamic change and you can enable/disable the dedicated lock manger on the fly. In some cases it can make a noticeable difference in database response. When originally introduced, VMS Engineering provided "it depends" as the definate answer on enabling it for your environment for servers with more than 4 CPUs.

Bottom line, schedule time and benchmark before and after. Don't forget to monitor CPU resouces as well, you'll be dedicating one CPU for this process.

Andy Bustamante

Re: How to identify processor manager req. for GS1280?

Hoff — Tue, 22 Dec 2009 18:53:17 GMT

Also look at what is obscurely known as Fast Path; at distributing I/O completion across your available processors.

http://h71000.www7.hp.com/doc/82final/5841/5841pro_069.html

topic How to identify processor manager req. for GS1280? in Operating System - OpenVMS

How to identify processor manager req. for GS1280?

Re: How to identify processor manager req. for GS1280?

Re: How to identify processor manager req. for GS1280?

Re: How to identify processor manager req. for GS1280?