Oh boy, similar name to me haha! ;)
Pengwin – A Linux Distro Optimized for WSL Based on Debian
31–40 of 93 posts
Re: Pengwin – A Linux Distro Optimized for WSL Based on Debian
#32Is WSL multithreaded? I love the ease of use that WSL gives, but it seems slow to cygwin on disk access. I think this is planned in a future fox by making the WSL directory to the disk instead of in a container file. I went back to cygwin for faster speed of scripts processing files.
It's only slow at file IO, yeah.
File IO can be vastly improved by excluding the WSL OS directory from Windows Defender real-time protection. Here's a gist that has powershell and GUI instructions for accomplishing this: https://gist.github.com/noelbundick/9c804a710eb76e1d6a234b14...
Re: Pengwin – A Linux Distro Optimized for WSL Based on Debian
#33Earlier quoted context omitted.
The filesystem is notably slower on Windows. It's easy to test it out for yourself; clone any big repo (eg: linux) in WSL and run `git status`. The Microsoft engineers have already done a lot of heroic efforts with WSL. The issue seems to be more inherent to the design and really hard to solve. ref: https://github.com/Microsoft/WSL/issues/873 To be clear, this is for a specific use-case. I don't believe that all appl…
It's definitely true in my experience that disk operations are slower in Windows. Folks on this thread are getting flack for poor comparisons (IMO Windows is worse at lots of small files), but even when you remove that, and say, look at mostly portable code that deals with a single file, as I have seen using sqlite as an example, it does worse. Not to mention Windows has built in antivirus reacting to all your filesy…
It's entirely possible to disable this by adding an exception for the WSL directory in Windows Defender. In my experience, this vastly improves IO from within linux.
Re: Pengwin – A Linux Distro Optimized for WSL Based on Debian
#34Earlier quoted context omitted.
It's definitely true in my experience that disk operations are slower in Windows. Folks on this thread are getting flack for poor comparisons (IMO Windows is worse at lots of small files), but even when you remove that, and say, look at mostly portable code that deals with a single file, as I have seen using sqlite as an example, it does worse. Not to mention Windows has built in antivirus reacting to all your filesy…
It's entirely possible to disable this by adding an exception for the WSL directory in Windows Defender. In my experience, this vastly improves IO from within linux.
I wasn't talking about WSL at all actually. I have never used it. Disk performance is just worse on Windows. With or without defender. (And defender is the default.)
Re: Pengwin – A Linux Distro Optimized for WSL Based on Debian
#35I tried looking around but didn't see anything about it. What makes this optimized for WSL?
Scroll down to Features on the linked page..
> Pengwin is also the first Linux distribution pre-configured and optimized to run specifically on Windows® Subsystem for Linux, a Microsoft-supported feature of Windows 10 and Windows Server 2019.
Yes. What kinds of optimizations make it optimized? This is my original question. Telling me the equivalent of "read the article" changes nothing when I've already done so and that it doesn't say what's been changed to make it optimized.
I've yet to carefully go through all 900 commits of with subject lines almost entirely of pull request #s, but one would think if whole repo's title was how it was "optimized" they could substantiate what they mean or what they did.
Re: Pengwin – A Linux Distro Optimized for WSL Based on Debian
#36Earlier quoted context omitted.
Scroll down to Features on the linked page..
> Pengwin is also the first Linux distribution pre-configured and optimized to run specifically on Windows® Subsystem for Linux, a Microsoft-supported feature of Windows 10 and Windows Server 2019. Yes. What kinds of optimizations make it optimized? This is my original question. Telling me the equivalent of "read the article" changes nothing when I've already done so and that it doesn't say what's been changed to mak…
I'm not sure if/what they changed in the distribution itself, but tooling optimizations are in the list:
* Pengwin includes wslu, a set of useful open-source utilities for interacting between WSL and Windows 10
* Manage your Microsoft Windows and Azure deployments with PowerShell and azure-cli, command line tools for Azure.
* Enable/disable Windows Explorer shell integration.
* Configure experimental GUI settings, including a Windows 10 theme for your Linux applications, HiDPI support and international input methods.
* Create a secure bridge to Docker running on Windows.
* Support for many Linux graphical applications with no need to configure display or libGL in Pengwin. (Requires a Windows-based X server, such as X410.)
* Pengwin provides faster patching for WSL-specific bugs than any upstream Linux distro available on WSL.
Re: Pengwin – A Linux Distro Optimized for WSL Based on Debian
#37Earlier quoted context omitted.
There's nothing to fix. The devices are either open and a dev has decided to write his own, or the devices are closed and the drivers are provided by their respective creators. If it's the former, pay a dev, if it's the latter, use a different device.
There's nothing to fix. The fire is either of a type that may be extinguished and a trained firefighter decided to put this type of fire out for everyone, or the fire is unable to be extinguished as was the intention of the entity that started it. If it's the former, find the correct firefighter, if it's the latter, use a different fire.
There's nothing to fix. The construction material is either of a type that does not spontaneously combust, and a carpenter can make you a fine chair out of it, or the material is the type to spontaneously combust, and if you choose to buy a chair made of that material you will soon find your pants are on fire.
If it's the former, pay a contractor to build you a chair, or make one yourself. If it's the latter, use a different construction material.
Re: Pengwin – A Linux Distro Optimized for WSL Based on Debian
#38Earlier quoted context omitted.
There's nothing to fix. The devices are either open and a dev has decided to write his own, or the devices are closed and the drivers are provided by their respective creators. If it's the former, pay a dev, if it's the latter, use a different device.
There's nothing to fix. The fire is either of a type that may be extinguished and a trained firefighter decided to put this type of fire out for everyone, or the fire is unable to be extinguished as was the intention of the entity that started it. If it's the former, find the correct firefighter, if it's the latter, use a different fire.
[deleted]
Re: Pengwin – A Linux Distro Optimized for WSL Based on Debian
#39Is WSL multithreaded? I love the ease of use that WSL gives, but it seems slow to cygwin on disk access. I think this is planned in a future fox by making the WSL directory to the disk instead of in a container file. I went back to cygwin for faster speed of scripts processing files.
I noticed file IO was slow too. My solution is to do most of my work in headless Linux VMs, using WSL as the interface to manage and connect to those VMs. This way I get the bash shell and ssh client I love but get isolated environments for my projects/clients. I run samba on the Linux VMs, with mapped drives on the Windows host so that I can edit files using VS Code. Outwardly it might look a little convoluted but I get isolation, performance, convinience and an ultra smooth host OS experience.
I say this coming from around a decade of running Linux or MacOS on the desktop. This just works.
Re: Pengwin – A Linux Distro Optimized for WSL Based on Debian
#40Interesting: “Grants/Bounties If you have an idea for a new feature you would like to see implemented in Pengwin and can implement it yourself given the funding, we are now accepting grant/bounty proposals. Grants are currently available for $50-$500 USD based on complexity.” The upper limit is quite demotivating, from my point of view.
Demotivating to whom? I imagine the intent is to avoid creating an impression that anyone has the power to make their pet issue priority #1 for the dev team just by throwing enough money at it.