The Black Bear - Threadripper 2990WX build


Recommended Posts

11 hours ago, jbartlett said:

So the key differences are:

  1. Yours is i440fx SeaBIOS and mine is Q35 OVMF
  2. You don't use <numatune> to fix RAM allocation across host NUMA nodes.
  3. You have <timer name='hpet' present='no'/> and mine is <timer name='hpet' present='yes'/>
  4. You don't spread load evenly across CCX and you also use core 0

Not sure which one(s) caused the diff in our test results though. My hunch is probably (2) or (4).

Link to comment

1. I got slightly better CPU scores under i440fx SeaBIOS than Q35 OVMF.

2. Still fine tuning CPU placement. One live test I ran last night showed CPU utilization steady on Cam2 taking in a NDI video feed jumped when Cam3 also started taking in a NDI video feed. Cam1 is hogging the CPUs with direct access to the memory and I may spread it out so it takes a numa node on memory and one off so I can move Cam2 & Cam3 on the numa nodes with memory. Ran a test just now and memory latency is 58.8% slower when it has to cross the Infinityfabric and the read/write/copy scores jump by 47% / 48.9% / 54% respectively.

Link to comment
On 12/17/2019 at 11:01 PM, testdasi said:

Someone asked me for the 12e BIOS for the Gigabyte X399 Designare EX, which has been replaced on Gigabyte website with the buggy 12i version.

So here it is attached - original zip file from Gigabyte.

mb_bios_x399-designare-ex_f12e.zip 6.1 MB · 3 downloads

Is it possible to write down all your Bios settings and the kernel parameters, well the settings that affects the working state of Unraid - KVM. Not boot settings etc.
Yesterday i did my build with Ex Designare and 2920x. Already had it die on me. One time it just crashed and giving me 500 internal error for GUI, could ping and ssh, but everything was unresponsive. even "htop" was blank. And today GUI was loading half pages, couldnt ssh and more.
Trouble passing through MB Audio.. 
Before making a huge post with details. Your settings will help make a good base. To test and post my problems orginized.

Thanks! And hopefully you will have sometime time to helm me, along with @SpaceInvaderOne to help me stabilize my new build! (As i saw on one of SI's videos he also have a 2950 *plus knowledge* :D) 

 

Just made a post about my build and loads of info/problems.  

 

Edited by skois
Link to comment
  • 3 weeks later...

@testdasi@jbartlett

Good news! I recently discovered that we no longer need the EPYC fix =0~~. Cache all comes through right and identifies as threadripper.. This should also translate for Ryzen as well.

All you need to do is change it to something like below(of course adjusting cores). All cache shows up properly, CPUZ launches and everything, things seem slightly more responsive and latency tests show same as baremetal. Happy days!

 

  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='8' threads='2'/>
    <cache mode='passthrough'/>

VM

image.png.4242de805a864fd07dac72bf72188523.png

Edited by Jerky_san
  • Thanks 3
Link to comment
2 minutes ago, Jerky_san said:

@testdasi@jbartlett

Good news! I recently discovered that we no longer need the EPYC fix =0~~. Cache all comes through right and identifies as threadripper.. This should also translate for Ryzen as well.

All you need to do is change it to something like below(of course adjusting cores). All cache shows up properly, CPUZ launches and everything, things seem slightly more responsive and latency tests show same as baremetal. Happy days!

 


  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='8' threads='2'/>
    <cache mode='passthrough'/>

 

Is there a reason for putting thread='2' ? Mine defaults at '1'.
 

Link to comment
1 minute ago, skois said:

Is there a reason for putting thread='2' ? Mine defaults at '1'.
 

You won't get properly threading sent to the OS. My understand is the OS will not schedule as well if it doesn't know which are "hyper threaded" and are not. If you don't have SMT enabled then this is a moot point..

Link to comment
2 minutes ago, Jerky_san said:

You won't get properly threading sent to the OS. My understand is the OS will not schedule as well if it doesn't know which are "hyper threaded" and are not. If you don't have SMT enabled then this is a moot point..

Do i have to do something on cpu allocations? Can you share your XML so i can see how you done it?
Does thread='2' means for every core is 2 threads
Or if i have e.g. 4 cores i have to do 8 threads?

I have SMT on, also i'm on a 2920x. which is a bit less confugsing with the numa nodes, i think it have a single numa only if not mistaken

Thanks!
 

Edited by skois
Link to comment
Just now, skois said:

Do i have to do something on cpu allocations? Can you share your XML so i can see how you done it?
Does thread='2' means for every core is 2 threads
Or if i have e.g. 4 cores i have to do 8 threads?

Thanks!
 

If you say have 8 cores assigned. 4 "physical" cores and 4 SMT cores then you'd say 4 cores 2 threads. PLEASE KEEP IN MIND the below is for a 2990wx configuration. If you don't have a 2990wx you do not need the NUMA tune or NUMA stuff.

 

  <vcpu placement='static'>16</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='4'/>
    <vcpupin vcpu='1' cpuset='36'/>
    <vcpupin vcpu='2' cpuset='5'/>
    <vcpupin vcpu='3' cpuset='37'/>
    <vcpupin vcpu='4' cpuset='6'/>
    <vcpupin vcpu='5' cpuset='38'/>
    <vcpupin vcpu='6' cpuset='7'/>
    <vcpupin vcpu='7' cpuset='39'/>
    <vcpupin vcpu='8' cpuset='8'/>
    <vcpupin vcpu='9' cpuset='40'/>
    <vcpupin vcpu='10' cpuset='9'/>
    <vcpupin vcpu='11' cpuset='41'/>
    <vcpupin vcpu='12' cpuset='10'/>
    <vcpupin vcpu='13' cpuset='42'/>
    <vcpupin vcpu='14' cpuset='11'/>
    <vcpupin vcpu='15' cpuset='43'/>
    <emulatorpin cpuset='4-11,36-43'/>
  </cputune>
  <numatune>
    <memory mode='strict' nodeset='0,2'/>
    <memnode cellid='0' mode='strict' nodeset='0'/>
    <memnode cellid='1' mode='strict' nodeset='2'/>
  </numatune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <vpindex state='on'/>
      <synic state='on'/>
      <stimer state='on'/>
      <reset state='on'/>
      <vendor_id state='on' value='KVM Hv'/>
      <frequencies state='on'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='8' threads='2'/>
    <cache mode='passthrough'/>
    <feature policy='require' name='topoext'/>
    <feature policy='disable' name='monitor'/>
    <feature policy='require' name='hypervisor'/>
    <feature policy='disable' name='svm'/>
    <feature policy='disable' name='x2apic'/>
    <numa>
      <cell id='0' cpus='0-7' memory='16777216' unit='KiB'/>
      <cell id='1' cpus='8-15' memory='16777216' unit='KiB'/>
    </numa>
  </cpu>

 

 

Link to comment
1 minute ago, Jerky_san said:

If you say have 8 cores assigned. 4 "physical" cores and 4 SMT cores then you'd say 4 cores 2 threads. PLEASE KEEP IN MIND the below is for a 2990wx configuration. If you don't have a 2990wx you do not need the NUMA tune or NUMA stuff.

 


  <vcpu placement='static'>16</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='4'/>
    <vcpupin vcpu='1' cpuset='36'/>
    <vcpupin vcpu='2' cpuset='5'/>
    <vcpupin vcpu='3' cpuset='37'/>
    <vcpupin vcpu='4' cpuset='6'/>
    <vcpupin vcpu='5' cpuset='38'/>
    <vcpupin vcpu='6' cpuset='7'/>
    <vcpupin vcpu='7' cpuset='39'/>
    <vcpupin vcpu='8' cpuset='8'/>
    <vcpupin vcpu='9' cpuset='40'/>
    <vcpupin vcpu='10' cpuset='9'/>
    <vcpupin vcpu='11' cpuset='41'/>
    <vcpupin vcpu='12' cpuset='10'/>
    <vcpupin vcpu='13' cpuset='42'/>
    <vcpupin vcpu='14' cpuset='11'/>
    <vcpupin vcpu='15' cpuset='43'/>
    <emulatorpin cpuset='4-11,36-43'/>
  </cputune>
  <numatune>
    <memory mode='strict' nodeset='0,2'/>
    <memnode cellid='0' mode='strict' nodeset='0'/>
    <memnode cellid='1' mode='strict' nodeset='2'/>
  </numatune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <vpindex state='on'/>
      <synic state='on'/>
      <stimer state='on'/>
      <reset state='on'/>
      <vendor_id state='on' value='KVM Hv'/>
      <frequencies state='on'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='8' threads='2'/>
    <cache mode='passthrough'/>
    <feature policy='require' name='topoext'/>
    <feature policy='disable' name='monitor'/>
    <feature policy='require' name='hypervisor'/>
    <feature policy='disable' name='svm'/>
    <feature policy='disable' name='x2apic'/>
    <numa>
      <cell id='0' cpus='0-7' memory='16777216' unit='KiB'/>
      <cell id='1' cpus='8-15' memory='16777216' unit='KiB'/>
    </numa>
  </cpu>

 

 

Thanks, yea ill avoid anything within numa, 
I'll have to research on what all those hyper-v optimizations you have there and the feature policies.!

Do you mind sharing on what motherboard you using?

Link to comment
1 minute ago, skois said:

Thanks, yea ill avoid anything within numa, 
I'll have to research on what all those hyper-v optimizations you have there and the feature policies.!

Do you mind sharing on what motherboard you using?

Asus x399 Zenith Extreme. The hyper-v stuff is to lower cpu consumption at idle.. There is also a timer thing as well that makes HPET enabled. Windows 10 will idle higher when signed off and will never let the CPU enter lower power states if you don't have the tweaks..

Link to comment
Just now, Jerky_san said:

Asus x399 Zenith Extreme. The hyper-v stuff is to lower cpu consumption at idle.. There is also a timer thing as well that makes HPET enabled. Windows 10 will idle higher when signed off and will never let the CPU enter lower power states if you don't have the tweaks..

I'll check those! i leave my VM up all day, so that should be good

 

Are you able to pass the onboard sound fine?
I'm having a problem with it not able to reset after i shut the vm down. Have to reset host so the sound is working again.
Kinda like the NAVI bug. 
im on X399 Ex Designare

Link to comment
Just now, skois said:

I'll check those! i leave my VM up all day, so that should be good

 

Are you able to pass the onboard sound fine?
I'm having a problem with it not able to reset after i shut the vm down. Have to reset host so the sound is working again.
Kinda like the NAVI bug. 
im on X399 Ex Designare

Mine will pass fine though a time or two it has randomly dropped out completely with the same sort of reset your talking about but it doesn't happen often. I went Zenith because it was the only card people confirmed worked with an LSI9201 card at the time. I actually have an ASRock X399 and it didn't ;-;

Link to comment
Just now, Jerky_san said:

Mine will pass fine though a time or two it has randomly dropped out completely with the same sort of reset your talking about but it doesn't happen often. I went Zenith because it was the only card people confirmed worked with an LSI9201 card at the time. I actually have an ASRock X399 and it didn't ;-;

Ouch, i get 

2020-01-05T19:58:20.209376Z qemu-system-x86_64: vfio: Cannot reset device 0000:0e:00.3, depends on group 22 which is not owned.
2020-01-05T19:58:21.295428Z qemu-system-x86_64: vfio: Cannot reset device 0000:0e:00.3, depends on group 22 which is not owned.

every time i start them. On next boot, it boots but no sound. have to suspend to memory.
well for now i do it anyway cause of the navi bug. but.. im looking to fix it :D

Link to comment
5 minutes ago, skois said:

Ouch, i get 


2020-01-05T19:58:20.209376Z qemu-system-x86_64: vfio: Cannot reset device 0000:0e:00.3, depends on group 22 which is not owned.
2020-01-05T19:58:21.295428Z qemu-system-x86_64: vfio: Cannot reset device 0000:0e:00.3, depends on group 22 which is not owned.

every time i start them. On next boot, it boots but no sound. have to suspend to memory.
well for now i do it anyway cause of the navi bug. but.. im looking to fix it :D

I get the same thing but audio all works every time I restart. Never doesn't at least. Below is my entire configuration. Maybe you can find something different.. I pass a 1080ti bios, NVME, and sound card. I need to remove the junk again. Just noticed it is all in there again.

2020-01-07T15:31:47.954105Z qemu-system-x86_64: vfio: Cannot reset device 0000:0c:00.3, depends on group 22 which is not owned.
2020-01-07T15:31:49.125110Z qemu-system-x86_64: vfio: Cannot reset device 0000:0c:00.3, depends on group 22 which is not owned.

 

 

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='4'>
  <name>Windows 10</name>
  <uuid>99642e81-2f13-a916-682c-90191636d75f</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>33554432</memory>
  <currentMemory unit='KiB'>33554432</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>16</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='4'/>
    <vcpupin vcpu='1' cpuset='36'/>
    <vcpupin vcpu='2' cpuset='5'/>
    <vcpupin vcpu='3' cpuset='37'/>
    <vcpupin vcpu='4' cpuset='6'/>
    <vcpupin vcpu='5' cpuset='38'/>
    <vcpupin vcpu='6' cpuset='7'/>
    <vcpupin vcpu='7' cpuset='39'/>
    <vcpupin vcpu='8' cpuset='8'/>
    <vcpupin vcpu='9' cpuset='40'/>
    <vcpupin vcpu='10' cpuset='9'/>
    <vcpupin vcpu='11' cpuset='41'/>
    <vcpupin vcpu='12' cpuset='10'/>
    <vcpupin vcpu='13' cpuset='42'/>
    <vcpupin vcpu='14' cpuset='11'/>
    <vcpupin vcpu='15' cpuset='43'/>
    <emulatorpin cpuset='4-11,36-43'/>
  </cputune>
  <numatune>
    <memory mode='strict' nodeset='0,2'/>
    <memnode cellid='0' mode='strict' nodeset='0'/>
    <memnode cellid='1' mode='strict' nodeset='2'/>
  </numatune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/99642e81-2f13-a916-682c-90191636d75f_VARS-pure-efi.fd</nvram>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <vpindex state='on'/>
      <synic state='on'/>
      <stimer state='on'/>
      <reset state='on'/>
      <vendor_id state='on' value='KVM Hv'/>
      <frequencies state='on'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='8' threads='2'/>
    <cache mode='passthrough'/>
    <feature policy='require' name='topoext'/>
    <feature policy='disable' name='monitor'/>
    <feature policy='require' name='hypervisor'/>
    <feature policy='disable' name='svm'/>
    <feature policy='disable' name='x2apic'/>
    <numa>
      <cell id='0' cpus='0-7' memory='16777216' unit='KiB'/>
      <cell id='1' cpus='8-15' memory='16777216' unit='KiB'/>
    </numa>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='yes'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <controller type='ide' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'>
      <alias name='pci.0'/>
    </controller>
    <controller type='usb' index='0' model='qemu-xhci' ports='15'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:23:bf:41'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/0'/>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/0'>
      <source path='/dev/pts/0'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-4-Windows 10/org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'>
      <alias name='input1'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input2'/>
    </input>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x43' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev0'/>
      <rom file='/mnt/user/domains/1080ti.rom'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0c' slot='0x00' function='0x3'/>
      </source>
      <alias name='hostdev1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x43' slot='0x00' function='0x1'/>
      </source>
      <alias name='hostdev2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x42' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev3'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x44' slot='0x00' function='0x3'/>
      </source>
      <alias name='hostdev4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
    </hostdev>
    <memballoon model='none'/>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+0:+100</label>
    <imagelabel>+0:+100</imagelabel>
  </seclabel>
</domain>

 

Edited by Jerky_san
Link to comment
3 hours ago, Jerky_san said:

If you say have 8 cores assigned. 4 "physical" cores and 4 SMT cores then you'd say 4 cores 2 threads. PLEASE KEEP IN MIND the below is for a 2990wx configuration. If you don't have a 2990wx you do not need the NUMA tune or NUMA stuff.

 


  <vcpu placement='static'>16</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='4'/>
    <vcpupin vcpu='1' cpuset='36'/>
    <vcpupin vcpu='2' cpuset='5'/>
    <vcpupin vcpu='3' cpuset='37'/>
    <vcpupin vcpu='4' cpuset='6'/>
    <vcpupin vcpu='5' cpuset='38'/>
    <vcpupin vcpu='6' cpuset='7'/>
    <vcpupin vcpu='7' cpuset='39'/>
    <vcpupin vcpu='8' cpuset='8'/>
    <vcpupin vcpu='9' cpuset='40'/>
    <vcpupin vcpu='10' cpuset='9'/>
    <vcpupin vcpu='11' cpuset='41'/>
    <vcpupin vcpu='12' cpuset='10'/>
    <vcpupin vcpu='13' cpuset='42'/>
    <vcpupin vcpu='14' cpuset='11'/>
    <vcpupin vcpu='15' cpuset='43'/>
    <emulatorpin cpuset='4-11,36-43'/>
  </cputune>
  <numatune>
    <memory mode='strict' nodeset='0,2'/>
    <memnode cellid='0' mode='strict' nodeset='0'/>
    <memnode cellid='1' mode='strict' nodeset='2'/>
  </numatune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <vpindex state='on'/>
      <synic state='on'/>
      <stimer state='on'/>
      <reset state='on'/>
      <vendor_id state='on' value='KVM Hv'/>
      <frequencies state='on'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='8' threads='2'/>
    <cache mode='passthrough'/>
    <feature policy='require' name='topoext'/>
    <feature policy='disable' name='monitor'/>
    <feature policy='require' name='hypervisor'/>
    <feature policy='disable' name='svm'/>
    <feature policy='disable' name='x2apic'/>
    <numa>
      <cell id='0' cpus='0-7' memory='16777216' unit='KiB'/>
      <cell id='1' cpus='8-15' memory='16777216' unit='KiB'/>
    </numa>
  </cpu>

 

 

Do you remember maybe where you got the info to put those <feature policy='xxx' name='xxx'/> flags and those in the hyperv? 
I'm trying to find info online that can help  me understand if i need them or not but cant find anything other than "how to format xml" or examples. but nothing that defines what exactly is each! Thanks!

Link to comment
1 minute ago, skois said:

Do you remember maybe where you got the info to put those <feature policy='xxx' name='xxx'/> flags and those in the hyperv? 
I'm trying to find info online that can help  me understand if i need them or not but cant find anything other than "how to format xml" or examples. but nothing that defines what exactly is each! Thanks!

https://github.com/qemu/qemu/blob/master/docs/hyperv.txt

 

https://www.reddit.com/r/VFIO/comments/d5z0cb/kvm_high_idle_use_in_win10/

Link to comment
8 hours ago, skois said:

Is there a reason for putting thread='2' ? Mine defaults at '1'.

AMD Threadripper doesn't support hyperthreadding out of the box to VM's but it can be tricked into working with the EPYC workaround. As such, the code behind the VM Editor is hard-coded to set the CPU threads to 1.

Link to comment

So by setting the threads to 2 and cores to half it enables hyperthreading, right? 

Or should I do something more? 

I did enable the hyperv settings and features policies mentioned by jerky_san. Didn't noticed any difference on usage but didn't do bad either. Cinebench scores was the same anyway. 

Link to comment
3 hours ago, skois said:

So by setting the threads to 2 and cores to half it enables hyperthreading, right? 

Or should I do something more? 

I did enable the hyperv settings and features policies mentioned by jerky_san. Didn't noticed any difference on usage but didn't do bad either. Cinebench scores was the same anyway. 

If you have a power meter. Measure the usage without logging out. Just sitting at the desktop. Then logout and see the usage drop. It is fairly be drop. Before at least on mine even with logging out the machine would be "idle" but in unraid you'd see lots of usage.

 

Also if you look at my CPUZ pic earlier you'll see at the bottom it says "8 cores 16 threads"

Edited by Jerky_san
Link to comment
2 hours ago, Jerky_san said:

If you have a power meter. Measure the usage without logging out. Just sitting at the desktop. Then logout and see the usage drop. It is fairly be drop. Before at least on mine even with logging out the machine would be "idle" but in unraid you'd see lots of usage.

 

Also if you look at my CPUZ pic earlier you'll see at the bottom it says "8 cores 16 threads"

Mine goes to idle on logout fine, i have a ups connected and i can see the power and also on webui unraid shows 1-2% usage on pinned cpus.
i was more intested in the hyperthreadding part! Would this give more performance? 
after setting cores 6 threads 2 on xml. CPU-Z  reports 6 cores 12 threads. so i guess hyper T is on!

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.