I'm setting up Performance Toolkit according to the instructions in "Getting Started with Linux on System z" for z/VM 5.4.0. This is just for a proof of concept, so I'm starting with the defaults. The PROFILE EXEC for MONWRITE on page 144 contains the following MONITOR EVENT commands:
'CP MONITOR EVENT ENABLE ALL' 'CP MONITOR EVENT DISABLE SEEKS ALL' 'CP MONITOR EVENT DISABLE USER ALL' 'CP MONITOR EVENT DISABLE SCHEDULER ALL' The PROFILE EXEC for PERFSVM on page 145 contains the following commands: 'CP MONITOR EVENT DISABLE ALL' 'CP MONITOR EVENT ENABLE STORAGE' 'CP MONITOR EVENT ENABLE I/O ALL' The settings of MONITOR EVENT APPLDATA, MONITOR EVENT NETWORK, and MONITOR EVENT PROCESSOR depend on which PROFILE EXEC is executed last. Are these events important? I don't expect to have applications generating events, so I don't think I care about APPLDATA. Varying processors on or off would be extremely rare. That leaves EVENT NETWORK. Are events such as virtual guest adapter initialization or termination valuable in performance analysis or problem diagnosis? Dennis "Of all tyrannies, a tyranny exercised for the good of its victims may be the most oppressive. It may be better to live under robber barons than omnipotent moral busybodies. The robber baron's cruelty may sometimes sleep, his cupidity may at some point be satiated; but those who torment us for our own good will torment us without end, for they do so with the approval of their own conscience." -- C.S. Lewis
