AFAIK, in the third level there is no SIE possible. That makes for a great performance impediment.
Kind regards, Willy -----Ursprüngliche Nachricht----- Von: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] Im Auftrag von Berry van Sleeuwen Gesendet: Mittwoch, 29. April 2009 12:01 An: IBMVM@LISTSERV.UARK.EDU Betreff: Re: Third level VSE Hello Kris, The guest runs with attached DASD so MDC is not applicable in this case. It doesn't look like IO is the problem here. But obviously any command processed in the guest will cause double the load in the host VM. So I do agree to avoid as much as possible. I don't know if MDC in the guest is possible or acceptable. Paging is not an issue. The host has 1G, the guest has 512M. The VSE runs NOPDS and the guest VM doesn't page. Yes, we run PTK. Running in the current config the guest VM can run up to 100%, and it does. When we assign 2 virtual CPU's to both VM and VSE (and start TD) we have seen the guest running up to about 190%. Also VSE does show processing at 100% CPU. But even an increase to 2 CPU's doesn't lower the transaction times for the transactions in question to an acceptable level. Regards, Berry.
