Jump to content

jbartlett

Community Developer
  • Content Count

    1492
  • Joined

  • Last visited

  • Days Won

    7

jbartlett last won the day on August 6 2019

jbartlett had the most liked content!

Community Reputation

161 Very Good

2 Followers

About jbartlett

  • Rank
    John Bartlett
  • Birthday 07/20/1970

Converted

  • Gender
    Male
  • URL
    https://www.youtube.com/c/TheCritterRoom/
  • Location
    Seattle, WA
  • Personal Text
    Foster parent for cats & kittens

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 6.8.1 RC 1 My passed through USB keyboard was still returned back to the OS during the Windows 10 boot process
  2. Did some on/off node testing with a TR 2990WX (off node = no direct access to ram/devices). Configured a VM with four numa nodes with two CPU's each (4 with HT) and 4 GB of RAM (1 GB per VM numa node), all set to hit against the same physical numa node. Tests were done on UNRAID 6.8.1 RC1 with the TR being passed through and the guest seeing both the hyperthreaded CPUs & NUMA nodes. Benchmarks were Cinemark R20 for CPU and AIDA64 for memory. Each score is an average of 5 runs with outlayers dropped (tested too far off the variance). Each pass moved a VM node from a numa node with direct access to one without. On Numa R20 Read Write Copy Latency 4 3663 31944 32558 32159 93.5 3 3645 30786 30483 30292 93.7 2 3587 27387 29982 27557 93.6 1 3607 19153 19809 20805 93.5 0 3526 14693 15097 17033 162.1 CPU scores saw a diminishing gain as the CPU's got moved off to a numa node without direct memory access as expected by the evenly spread score was surprisingly low. Memory scores shows a clear benefit to having at least one CPU on node in memory access with the times being negatively impacted nearly 100% being completely isolated.
  3. I'm passing through my TR on 6.8.1 RC1 with no hacks or workarounds (but does need the topoext cpu flag) and getting hyperthreadding. I recommend upgrading. I haven't finished my benchmarking yet but am seeing some small improvements.
  4. Here's the controller link report for the 0000:08:00.0 device 08:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05) Capabilities: [68] Express (v2) Endpoint, MSI 00 LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM L0s, Exit Latency L0s <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ LnkSta: Speed 8GT/s, Width x8, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- I have a lookup table that for PCI3 with a transfer rate of 8 and a width of 8 returns "7.88 GB/s". It looks like this reference table is in error. Based on information from https://paolozaino.wordpress.com/2013/05/21/converting-gts-to-gbps/ I should be able to compute it. The transfer rate of 8 GT/s identifies it as a PCI 3 controller. 8 GT/s multiplied by 8 lanes equals 64 GT/s, multiplied by the overhead (LineCodeL/LineCodeH) of 128b/130b equals 63.02 GB/s.
  5. @icemansid - Please upload/email a debug file from the DiskSpeed app (link at the bottom of the page). Use the left button to create a regular/smaller report. The link speed uses the results from a lspci -vmm command and the debug file will have what it returned.
  6. The DiskSpeed app simply reports what the dd command is outputting. If you're having issues reading all the drives at once, try removing half of the drives and then run a controller benchmark to see if you get the same results or better. If the same, remove the existing and hook the others back up. If better, then add a couple drives and do another benchmark. Rinse & repeat. See if there's a magic number or a given drive that's causing the issue.
  7. @bonienl The VM GUI editor is hard coded to set the thread count to 1 if it detects an AMD processor in libvirt.php // detect if the processor is AMD, and if so, force single threaded $strCPUInfo = file_get_contents('/proc/cpuinfo'); if (strpos($strCPUInfo, 'AuthenticAMD') !== false) { $intCPUThreadsPerCore = 1; } This was due to AMD reporting no support for hyperthreadding in a VM. With UNRAID 6.8.1 RC1, hyperthreadding is supported with CPU passthrough as is (and CPU cache) if the CPU feature topoext is enabled. Previously, the CPU had to be forced to report as an EPYC to get it to support hyperthreadding. <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='6' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> Microsoft's CoreInfo returns Coreinfo v3.31 - Dump information on system CPU and memory topology Copyright (C) 2008-2014 Mark Russinovich Sysinternals - www.sysinternals.com Logical to Physical Processor Map: **---------- Physical Processor 0 (Hyperthreaded) --**-------- Physical Processor 1 (Hyperthreaded) ----**------ Physical Processor 2 (Hyperthreaded) ------**---- Physical Processor 3 (Hyperthreaded) --------**-- Physical Processor 4 (Hyperthreaded) ----------** Physical Processor 5 (Hyperthreaded) Note that changes to the CPU layout may not be detected in the VM until the VM is rebooted from inside the VM itself (for example: Start > Power > Restart) Prior to 6.8.1 RC1, I could not get CPU-Z to run, it would always hang at the 10%/Processors on load. It still takes a bit but does return now.
  8. CONFIRMED: On 6.8.1 RC1, I don't need the EPYC workaround to get hyperthreadding enabled but the TR does need the following CPU feature: <feature policy='require' name='topoext'/> I was also able to get CPU-Z to run with CPU passthrough and hyperthreading detected though it takes a bit at the 10%/Processors stage where in the past it apparently hung. I'm going to look to see if HT support has already been recommended for Threadripper CPUs and request it if not.
  9. Thanks for mentioning "virtio", that reminded me to check for a new virtio-win ISO file. New one out last October, version 0.1.173.2
  10. Ya know, you just invalidated 4 benchmark runs with 25 passes each run. At least you caught be before the next two runs! 😁 Might as well upgrade to 6.8.1 RC1 too. Though this would also mean a lot less edits in the XML every time I needed to use the GUI editor.
  11. Can you install Microsoft's CoreInfo and see if it detects a hyperthreaded setup? I use this Batch file for a quick report since it's a command line utility and the screen will close after running Coreinfo.bat @echo off coreinfo.exe -ncs pause My Results with the EPYC hyperthreading workaround (weird numa mapping due to cross-numa node testing) Coreinfo v3.31 - Dump information on system CPU and memory topology Copyright (C) 2008-2014 Mark Russinovich Sysinternals - www.sysinternals.com Logical to Physical Processor Map: **---------- Physical Processor 0 (Hyperthreaded) --**-------- Physical Processor 1 (Hyperthreaded) ----**------ Physical Processor 2 (Hyperthreaded) ------**---- Physical Processor 3 (Hyperthreaded) --------**-- Physical Processor 4 (Hyperthreaded) ----------** Physical Processor 5 (Hyperthreaded) Logical Processor to Socket Map: ************ Socket 0 Logical Processor to NUMA Node Map: **---------- NUMA Node 0 --********** NUMA Node 1 Press any key to continue . . .
  12. 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.