From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 2197E6C975 for ; Tue, 30 Mar 2021 14:35:37 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0D4852A9CD for ; Tue, 30 Mar 2021 14:35:07 +0200 (CEST) Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 7BF8A2A9B6 for ; Tue, 30 Mar 2021 14:35:03 +0200 (CEST) Received: by mail-lf1-x131.google.com with SMTP id v15so23528602lfq.5 for ; Tue, 30 Mar 2021 05:35:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tecnetmza-com-ar.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=9tTi3/I3E9YYBIS9tJhpIjQoejg2R1tXjvzSqRmVb1w=; b=yXswUv5pjyDgTykoKlhujKCX4qXn0LzAnc1qCS/tnywI3ErROJl53lhwvXljnTpk6c ldqYfWNCYuhoX/Lti9KlqxxcQMIhHT8T3RQhuzQ56lrIiZddTnLeNxsMDdeBdFiwUInF j8TYjRLo6r5hT+zb5aapJ7Lf9ZobdM4sUK9pxUuwx1nGvv7XunCraogpPch5D2w2bdAH A5SAKhSMSw2wY6g4aQyY/DQ2pHDDzeOrfqtiQI6wW+34jhs33BDRDfy/NJ2aPx28dSOa 9HGrEee/+YLRPMD+FYtE9hvrqtHR2CRfFFXIk1yp+2LHN06NKiq2mYS3v8wARCfzpap/ NHpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=9tTi3/I3E9YYBIS9tJhpIjQoejg2R1tXjvzSqRmVb1w=; b=dMcnER39M3oLGJau9IGUHeEl6evODVttBakC78dEWRPM8ijXsPPMxiPCe2Mqxz87om 7OHSvmy+zFqt71hXhE4QsmaSrpKiZ28HHG4S6gz5jgEARJ0K9GklLIvIApAGm03eWR3/ qnxB+TrTdyeAQ91APXLZuwMjbNZe+ABFsEBtUD9uh5fJa6SNUMO7dVvWCKpzCYziLOkO uuJOM2APcBIDtNlu44LBocAqt1odFO8HNL9w5CSA3pG4AJanEJ+aXy2kux+x5nagyq6c vo9UZAAk69auXgR0ktdJCk2+vkFnMSFmNOviyNv9u4Y04JBz8X4vq+MusJNSEKaG+CSD j9Fg== X-Gm-Message-State: AOAM532rDTVYQI+6Dketrhkt0KcHzgspxRFaA8U4pcDekomj2UEjR+6/ mAzwb/INFBsgSht6H+ZR0tdFBBIWmd0eSTAevNRu X-Google-Smtp-Source: ABdhPJxeFBAZZ+wOshB3fWOlV/q8IVxbKfxfypHurkvZ9CJg3htJhbygnlIumWtz1HiBXx5qlQqBeunQ4pcYLUti/XA= X-Received: by 2002:a19:5005:: with SMTP id e5mr20572490lfb.109.1617107696820; Tue, 30 Mar 2021 05:34:56 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Leandro Roggerone Date: Tue, 30 Mar 2021 09:34:44 -0300 Message-ID: To: Arjen , Proxmox VE user list X-SPAM-LEVEL: Spam detection results: 1 AWL 0.182 Adjusted score from AWL reputation of From: address DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature HTML_MESSAGE 0.001 HTML included in message RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_SOFTFAIL 0.972 SPF: sender does not match SPF record (softfail) URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [fedorapeople.org, proxmox.com] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [PVE-User] Windows sever 2016 vm with very high ram usage X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Mar 2021 12:35:37 -0000 Hi guys / Arjen. My windows server performance is definitely much better now , I will try more cpu combinations, and have last question regarding this ? Is there some documentation about this ? how can I analize and choose my cpu setting ? About performances testing: Is there some recommended way to benchmark cpu settings ? Thanks guys for your help. (let me know if you came to mendoza ... I will glad to invite you dinner). Leandro. El lun, 29 mar 2021 a las 11:47, Arjen via pve-user (< pve-user@lists.proxmox.com>) escribi=C3=B3: > > > > ---------- Forwarded message ---------- > From: Arjen > To: Proxmox VE user list > Cc: > Bcc: > Date: Mon, 29 Mar 2021 14:46:08 +0000 > Subject: Re: [PVE-User] Windows sever 2016 vm with very high ram usage > On Monday, March 29th, 2021 at 16:30, Leandro Roggerone < > leandro@tecnetmza.com.ar> wrote: > > > Dear Arjen , nice data you provided , im trying it right now. > > > > > BTW , after installing virtIO drivers , memory usage looks ok on the > > > > > proxmox gui (very nice!). > > > > > Regarding CPU layout , I understood this: > > > > > I should use just one socket , so in my case would be 1socket x 6 cores= , > > > > > total 6 vCPUs. > > > > > If I notice that cpu usage goes high , lets suppose over 85% , I should > add > > > > > a second socket and enable NUMA. > > That CPU has 12 threads (right?), so you can try up to 12 vCPUs. And > select 'host' or a CPU type that is close to your physical CPU instead of > the kvm64 default. Maybe enabling NUMA helps even with less virtual cores= , > just try it and compare performance. If you enable NUMA, choose the same > number of virtual sockets as real sockets (=3D2). Remember that the amoun= t of > vCPUs is cores multiplied by the number of sockets. Maybe you can try 6x1 > or 3x2 or 12x1 or 6x2 and see which performs the best? > > > I will change ide for scsi as you suggested. > > > > > No problem if I need to re install OS. > > You can find the Windows drivers for VirtIO here: > > https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-= virtio/virtio-win-0.1.185-2/ > > > Regards. > > > > > Leandro. > > > > > El lun, 29 mar 2021 a las 10:57, Arjen via pve-user (< > > > > > pve-user@lists.proxmox.com>) escribi=C3=B3: > > > > > > ---------- Forwarded message ---------- > > > > > > > From: Arjen leesteken@protonmail.ch > > > > > > > To: Proxmox VE user list pve-user@lists.proxmox.com > > > > > > > Cc: > > > > > > > Bcc: > > > > > > > Date: Mon, 29 Mar 2021 13:56:59 +0000 > > > > > > > Subject: Re: [PVE-User] Windows sever 2016 vm with very high ram usag= e > > > > > > > On Monday, March 29th, 2021 at 15:37, Leandro Roggerone < > > > > > > > leandro@tecnetmza.com.ar> wrote: > > > > > > > > Hi guys , thanks for your words , have some feedback: > > > > > > > > Maybe Proxmox cannot look inside the VM for the actual memory usage > > > > > > > > > because > > > > > > > > the VirtIO balloon driver is not installed or active? Or maybe the > other > > > > > > > > 90% is in use as Windows file cache? > > > > > > > > I think so ... > > > > > > > > Dont know about windows file cache ... > > > > > > > > Have you installed the VirtIO drivers for Windows? Are you assignin= g > too > > > > > > > > many vCPUs or memory? Can you share the VM configuration file? Can > you > > > > > > > > > tell > > > > > > > > us something about your Proxmox hardware and version? > > > > > > > > No , I have not ... now you mentioned im reading about VirtIO , I > will > > > > > > > > > try > > > > > > > > to install and let you know how it goes > > > > > > > > Should install it no my pve box or directly inside windows vm ? > > > > > > > > I'm assigning max vCPUs abailables (24 , 4 sockets 6 cores) and 32g= b > for > > > > > > > > memory. > > > > > > > > (I really don't know about any criteria to assign vcpus) > > > > > > > > This is VM config file: > > > > > > > > root@pve:~# cat /etc/pve/nodes/pve/qemu-server/107.conf > > > > > > > > bootdisk: ide0 > > > > > > > > cores: 6 > > > > > > > > ide0: local-lvm:vm-107-disk-0,size=3D150G > > > > > > > > ide1: local-lvm:vm-107-disk-1,size=3D350G > > > > > > > > ide2: > > > > > > > > local:iso/Windows_Server_2016_Datacenter_EVAL_en-us_14393_refresh.ISO,med= ia=3Dcdrom,size=3D6808810K > > > > > > > > memory: 32768 > > > > > > > > name: KAIKENII > > > > > > > > net0: e1000=3D1A:F1:10:BF:92:0A,bridge=3Dvmbr3,firewall=3D1 > > > > > > > > numa: 0 > > > > > > > > ostype: win10 > > > > > > > > scsihw: virtio-scsi-pci > > > > > > > > smbios1: uuid=3Ddaf8f767-59c7-4e87-b3be-75d4a8020c38 > > > > > > > > sockets: 4 > > > > > > > > vmgenid: a7634624-1230-4a3e-9e7c-255d32ad2030 > > > > > > > > My PVE is: > > > > > > > > CPU(s) 24 x Intel(R) Xeon(R) CPU X5680 @ 3.33GHz (2 Sockets) > > > > > > > > Kernel Version Linux 5.0.15-1-pve #1 SMP PVE 5.0.15-1 (Wed, 03 Jul > 2019 > > > > > > > > 10:51:57 +0200) > > > > > > > > PVE Manager Version pve-manager/6.0-4/2a719255 > > > > > > > > Total Mem =3D 64GB. > > > > > > > > That's all. > > > > > > > > Thanks > > > > > > > You are using emulated IDE drives, which is very slow. Please install > the > > > > > > > VirtIO SCSI driver for Windows inside the VM and attach the disk with > > > > > > > (vitual) scsi instead of ide. You might need to reinstall Windows to > make > > > > > > > it boot. Use the VirtIO virtual floppy to install the VirtIO SCSI > driver > > > > > > > when starting the Windows installation setup inside the VM. > > > > > > > Use as little virtual cores and as little memory as is needed (or jus= t > a > > > > > > > little more), this makes the VM run more smoothly. You systems has tw= o > > > > > > > sockets, so you might want to enable NUMA in the VM configuration, > > > > > > > otherwise your VM memory access has to go to the other socket often, > which > > > > > > > is slow. Using just the cores from one of your CPU's (or less) will > perform > > > > > > > better than using all for the same reason of less communication betwe= en > > > > > > > physical sockets. > > > > > > > Currently, you have chosen all the slowest options to run this VM on > your > > > > > > > kind of system. Each of the steps above will increase performance. Th= e > > > > > > > VirtIO driver installation is the most work, but also gives the most > > > > > > > performance increase. Selecting 'host' instead of kvm64 will also > improve > > > > > > > performance. > > > > > > > kind regards, Arjen > > > > > > > > El vie, 26 mar 2021 a las 11:40, Arjen via pve-user (< > > > > > > > > pve-user@lists.proxmox.com>) escribi=C3=B3: > > > > > > > > > ---------- Forwarded message ---------- > > > > > > > > > From: Arjen leesteken@protonmail.ch > > > > > > > > > To: Proxmox VE user list pve-user@lists.proxmox.com > > > > > > > > > Cc: > > > > > > > > > Bcc: > > > > > > > > > Date: Fri, 26 Mar 2021 14:39:13 +0000 > > > > > > > > > Subject: Re: [PVE-User] Windows sever 2016 vm with very high ram > usage > > > > > > > > > On Friday, March 26th, 2021 at 15:28, Leandro Roggerone < > > > > > > > > > leandro@tecnetmza.com.ar> wrote: > > > > > > > > > > Hi guys , Just wanted to share this with you. > > > > > > > > > > After creating a VM for a windows sever 2016 with 32 GB ram I c= an > > > > > > > > > > see continuos high memory usage (about 99-100%). > > > > > > > > > > I have no running task , since it is a fresh server and from ta= sk > > > > > > > > > > > > > manager > > > > > > > > > > can see a 10% of memory usage. > > > > > > > > > > Regarding those confusing differences, server performance is ve= ry > > > > > > > > > > > > > bad. > > > > > > > > > Maybe Proxmox cannot look inside the VM for the actual memory usa= ge > > > > > > > > > because the VirtIO balloon driver is not installed or active? Or > maybe > > > > > > > > > > > the > > > > > > > > > other 90% is in use as Windows file cache? > > > > > > > > > > User experience is very poor with a non fluent user interface. > > > > > > > > > > Is there something to do / check to improve this ? > > > > > > > > > Have you installed the VirtIO drivers for Windows? Are you > assigning > > > > > > > > > > > too > > > > > > > > > many vCPUs or memory? Can you share the VM configuration file? Ca= n > you > > > > > > > > > > > tell > > > > > > > > > us something about your Proxmox hardware and version? > > > > > > > > > > Any advice would be welcome. > > > > > > > > > Maybe search the forum for similar Windows performance questions? > > > > > > > > https://forum.proxmox.com/forums/proxmox-ve-installation-and-configuratio= n.16/ > > > > > > > > > > Thanks. > > > > > > > > > best of luck, Arjen > > > > > > > > > ---------- Forwarded message ---------- > > > > > > > > > From: Arjen via pve-user pve-user@lists.proxmox.com > > > > > > > > > To: Proxmox VE user list pve-user@lists.proxmox.com > > > > > > > > > Cc: Arjen leesteken@protonmail.ch > > > > > > > > > Bcc: > > > > > > > > > Date: Fri, 26 Mar 2021 14:39:13 +0000 > > > > > > > > > Subject: Re: [PVE-User] Windows sever 2016 vm with very high ram > usage > > > > > > > > > pve-user mailing list > > > > > > > > > pve-user@lists.proxmox.com > > > > > > > > > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > > > > > > > pve-user mailing list > > > > > > > > pve-user@lists.proxmox.com > > > > > > > > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > > > > > > ---------- Forwarded message ---------- > > > > > > > From: Arjen via pve-user pve-user@lists.proxmox.com > > > > > > > To: Proxmox VE user list pve-user@lists.proxmox.com > > > > > > > Cc: Arjen leesteken@protonmail.ch > > > > > > > Bcc: > > > > > > > Date: Mon, 29 Mar 2021 13:56:59 +0000 > > > > > > > Subject: Re: [PVE-User] Windows sever 2016 vm with very high ram usag= e > > > > > > > pve-user mailing list > > > > > > > pve-user@lists.proxmox.com > > > > > > > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > > > > pve-user mailing list > > > > > pve-user@lists.proxmox.com > > > > > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > > ---------- Forwarded message ---------- > From: Arjen via pve-user > To: Proxmox VE user list > Cc: Arjen > Bcc: > Date: Mon, 29 Mar 2021 14:46:08 +0000 > Subject: Re: [PVE-User] Windows sever 2016 vm with very high ram usage > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user >