Re: VM system name

2020-08-03 Thread Timothy Sipples
Would this readout make better sense? $ zhypinfo NoLayer TypeName IFL CP -- 2.2 z/VM_Guest guest myguest2 0 2.1 z/VM_Resource_Pool poolpooltest

Re: Overcommitting zLinux CPU

2020-08-03 Thread Berry van Sleeuwen
I'd say have multiple guests. Let's NOT forget SPOF. (Well, you have a SPOF if it's in only one z/VM LPAR but at least you have multiple guests that can be serviced at different times.) I usually like a number of small guests over a single large guest. Especially when there are multiple

Re: Overcommitting zLinux CPU

2020-08-03 Thread Mariusz Walczak
Hello, I also thought that enabling SMT will degrade performance of a single threaded process, but I could not find anyone to confirm that. Thank you Christian. Alan: Postgres is not constrained by having only 4 cores. It's running fine with 1 vCPU. The problem is with overall Openshift Cluster

Re: VM system name

2020-08-03 Thread Stefan Raspl
On 2020-07-18 20:58, Mark Post wrote: > On 7/17/20 12:18 PM, Marcy Cortes wrote: >> Late to the game, but I would probably make a .service file that did >> something like >> >> ExecStart= echo $(/sbin/vmcp q userid | awk '{print $3}') > /etc/vmsysname >> >> and then anything could look at the

Re: Overcommitting zLinux CPU

2020-08-03 Thread Christian Borntraeger
On 02.08.20 06:36, Alan Altmark wrote: > > A physical core has a certain amount of “horsepower” in it. It can, at top > speed do X amount of work. > > In SMT, you split the core in half, creating two execution contexts (CPUs) > instead of just one. The two CPUs share resources on the physical