• 0 Posts
  • 38 Comments
Joined 2 years ago
cake
Cake day: June 19th, 2023

help-circle
  • The start menu being React Native is irrelevant. If it were React in an Edge web view that would be a different story.

    Opening the start menu should cause a spike in CPU usage. You want the CPU to open the menu ASAP instead of dragging out the process so the CPU usage is more flat.

    But everything in Windows these days is wasting time stealing your data, loading ads or other unnecessary data from cloud services, and interacting with “AI.” Performance is one of the lowest priorities, somewhere between software quality and privacy. Since mid Windows 10, Microsoft consistently replaces things with modernized, but worse, versions and never returns to finish making the new version as good as the previous version that evolved over decades. It’s a really expensive way to ruin a product. They could make a React Native start menu where people wouldn’t complain about the performance. They probably did and people are only noticing now because of a recent regression.













  • Borg / k8s / Docker are not the same thing. Borg is the predecessor of k8s, a serious tool for running production software. Docker is the predecessor of Podman. They all use containers, but Borg / k8s manage complete software deployments (usually featuring processes running in containers) while Docker / Podman only run containers. Docker / Podman are better for development or small temporary deployments. Docker is a company that has moved features from their free software into paid software. Podman is run by RedHat.

    There are a lot of publicly available container images out there, and most of them are poorly constructed, obsolete, unreprodicible, unverifiable, vulnerable software, uploaded by some random stranger who at one point wanted to host something.


  • VLANs are lower than IP so you don’t need a router to have a VLAN, but you will need a router to get packets between the networks. I don’t think a WiFi repeater works. You likely need separate WiFi client and AP devices so you can put your WiFi on a different channel. Otherwise you’re probably halving your WiFi performance when connecting to the other network over the same airwaves.

    Unless you can convince the other network to route your IP addresses, this setup will give you another layer of NAT and may cause problems with online games.







  • First, it’s not possible to use “pure docker” on Windows. Docker is for running additional user mode environments under the same kernel. You can’t run Linux applications under the Windows kernel without WSL1, and WSL1’s Linux implementation does not support the features required for Docker. This is also possible in limited cases with Windows Server, but because of differences in the way Windows works you almost always end up running a second kernel.

    WSL2 can be used to run Docker, and in fact that’s how Docker Desktop works since years ago. When you start Docker Desktop it starts a WSL2 distribution under which the containers run. Running Docker from the command line only will not positively change the performance of your containers.

    Running other virtualization software, especially VirtualBox, to start a separate Linux VM and running your containers in there is going to be more complicated and give worse performance unless you disable all virtualization-based features of Windows, such as WSL2 and security isolation.

    The solution to your memory problem is most likely one of the following:

    1. Don’t disable the pagefile. Windows uses a weird memory model where all virtual memory must be backed by physical memory. Certain software will allocate virtual memory without using it, and Windows will require that the sum of the physical memory size and the page file size be adequate to use all of that virtual memory. Disabling the pagefile or limiting it to small sizes because you “have enough RAM” will cause out of memory errors while you still have plenty of RAM available.
    2. Reduce the amount of memory that Docker is allowed to use to a level that your Windows software can tolerate. You may need to switch Docker Desktop to Hyper-V mode for this option to be available, which isn’t an option if you’re on Windows Home, and this may reduce compatibility.
    3. After stopping your containers, run echo 1 > /proc/sys/vm/compact_memory at a WSL2 prompt or wsl -u root -- bash -c 'echo 1 > /proc/sys/vm/compact_memory' from a Windows prompt. See Memory Reclaim in the Windows Subsystem for Linux 2 for details about what this does.