4 ms·
The ratio of bad to good posts has always stunned me too. But for the opposite reason. The linked post explains that there is a performance regression in a ver
by thomaszander 6y ago
The ratio of bad to good posts has always stunned me too. But for the opposite reason.
The linked post explains that there is a performance regression in a very rare and specific usecase: creating 100k files in a short span of time. And I'm not talking about unpacking boost, that's not enough files.
Additionally, it will be fixed before any distro packages it. (even Arch is still on 5.9.14.)
On the other hand btrfs got rather impressive speedups for fsync
https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.10-Btrfs-Fsync-Faster https://www.phoronix.com/scan.php?page=news_item&px=Linux-5....
Why are people making so much noise instead of just reporting the bug upstream when stuff goes wrong with btrfs, and why do we hear so little about the positive impact of new improvements. Almost like the people behave like customers of commercial operating systems. :-)
- scaladev 6y ago>creating 100k files in a short span of time. And I'm not talking about unpacking boost, that's not enough files. In JavaScript world that's really not that much. A project I've been working on has 120k+ files in node_modules, and `yarn install` creates the whole directory tree in a few seconds. It's not some obscure issue nobody ever runs into.
- minot 6y agoNot btrfs and anecdotal but fedora 33 / 5.8 kernel / default gnome was unusable for me on amd r5 3500U. Headphone microphone didn’t work. Bluetooth ear phones and mic didn’t work. USB headphone microphone worked though. Sure enough most of the issues were resolved by 5.9 but I can no longer recommend Linux on the desktop.
- motakraxxer 6y agoWith the problems you are listing, you would have never been able to recommend Linux. The problem stem from lack of driver support in the kernel for the devices on your machine. If that is the case, then your machine maker obviously does not support linux. So, it's no surprise that your machine had problems with linux. If you buy a machine that supports linux, you would not see those problems. Nothing to do with linux, mostly to do with interaction of linux and your machine manufacturer.
- minot 6y agoSorry I failed to mention that things were much better before the update. Sure the fingerprint reader goodix never worked but the things I mentioned above are regressions. I’m all in favor of wayland but if we say we remove existing working features (fedora 32) because security or whatever we might as well wear tin foil hats and stay away from computers.
- simion314 6y agoI suggest you try Ubuntu LTS (not latest) or Debian less coolness factor but you don't get regression because only security updates are happening. Your hardware must be compatible and you need to resist the urge to get the latest shiny stuff.
- therealrootuser 6y agoOver the last 15 years, I've run a lot of distros on a lot of different hardware. On desktop, Fedora has been by far the most reliable. Ubuntu LTS, as far as I can tell from using it for work, just means that annoying bugs that have been fixed in the upstream never get backported. Case in point: Bluetooth on Ubuntu LTS has always been much less reliable for me than on Fedora. Disclaimer: This is only my anecdotal experience, use whatever works best for you.
- simion314 6y agoYou can't have it both ways, you can't get only the bug fixes without the new bugs , except on LTS you can if you know how experiment with getting a new kernel or video driver but not updating your DE,
- minot 6y ago> getting a new kernel > you can't get only the bug fixes without the new bugs > if you know how experiment with getting a new kernel or video driver I would agree with you if I was on my old machine with an nVidia graphics card which for what it is worth my new machine is a much better experience with AMD processor and integrated graphics but still how do you explain audio in failing to work as soon as I upgraded to Fedora 33 / kernel 5.8 and it (mostly) resolving itself when upgrading to 5.9 kernel? Is this a kernel bug or not? What caused it? What can we do to prevent it from happening in the future?
- m1gu3l 6y agothis is fair and i will cop to most of my exp in linux being in the "mainstream"/"commercial" filesystems. guilty as charged :)