• Absolutely nothing.
  
  
  
  
  
  
• The Ryzen 4700G has poked its nose above the waterline.  (Tom's Hardware)
  
  It looks like a fully-configured Ryzen 4000 APU - 8 cores, 8 CUs, 8MB cache.  With a desktop TDP and fast RAM it should be a pretty solid workhorse.  It probably only supports PCIe 3.0, but has the same lane configuration as existing dekstop Ryzens so that's not a huge drawback.
  
  
  
• The 4900U has also been spotted in benchmark results unless that was swamp gas reflecting off the surface of Venus.  (WCCFTech)
  
  It's a very minor tweak to the 4800U, though.
  
  
  
• Meanwhile the Core i9-10900K uses 235W at 4.8GHz and is hot enough to boil molasses in January, as the kids say.  (WCCFTech)
  
  Using a 240mm all-in-one water cooler it ran at an average temperature of 87C under load.  Higher clock speeds are temperature-controlled - it has to be running at 70C or lower to hit top speed - so that gives you an idea of what you'll need in the way of cooling.
  
  Liquid nitrogen it is then.
  
  
  
• I got LXD virtual machines (as opposed to containers) working on Akane III.  It's completely painless to start a virtual machine under LXD 4.0 - you just use the same launch command as you would with a container and add --vm.
  
  Few differences: By default containers give you full access to the system's resources - though not control over them - and you can set limits on CPU, memory, and disk for individual containers or create profiles to apply the same limits across multiple containers.  And you can change all the settings live.
  
  Virtual machines start by default with one core, 1GB RAM, and 2GB of disk.  And a very stripped down version of Linux with broken networking.  Which means that you can't install new packages because it can't reach the server where the packages live.
  
  What I found today was the right sequence of commands with what is available in the minimal install to get networking working:

  ip addr add 10.1.1.21/24 dev enp5s0
ip link set enp5s0 up
ip route add default via 10.1.1.1 dev enp5s0
echo "nameserver 8.8.8.8" > /etc/resolv.conf

  None of which will survive a reboot, though you can just stick it in /etc/rc.local as a quick fix.
  
  I'm not sure which of the three or four network configuration tools is supposed to be active, but none of them actually are, so it probably doesn't matter a whole lot.
  
  I managed to reconfigure the memory and CPU settings; apart from requiring a reboot that works exactly the same as with containers.  Increasing the disk space, however, didn't work at all.  I suspect that has to be done when you create the VM.
  
  I plan to run a speed comparison with my Python benchmark to compare running directly on the OS with running in a container (which should perform basically the same) with running in a full virtual machine (which anecdotally can be significantly slower) with running in a container inside a virtual machine.
  
  That last because it would be the easiest way to migrate this server - the one hosting this blog.  In fact, it is how this server is running right now, though with older virtualisation and container software.
  
  The new CPU is about 70% faster, and I'd like to see if the new software is also faster.

Posted by: Rick C at Wednesday, May 13 2020 12:32 AM (Iwkd4)

Posted by: Pixy Misa at Wednesday, May 13 2020 02:00 AM (PiXy!)

Posted by: Pixy Misa at Thursday, May 14 2020 05:15 PM (PiXy!)

Hide Comments | Add Comment