> "Thinking this will prevent war, the US government gives an impenetrable supercomputer total control over launching nuclear missiles"
That's not even close to what the Golden Dome is.
> The Golden Dome is a planned multi-layer missile defense system for the United States, intended to detect and destroy ballistic, hypersonic, and cruise missiles before they launch or during their flight.
Well then I was a one off. It got me (along with how slow it was) to leave. Maybe it was a bug? Maybe I misconfigured it? Maybe it was OS? Who knows? Glad it works for you.
This was using the local web server instance to manage permissions for users, so maybe every time my distro undated the web server software or something. Either way, for my use case it didn't work out of the box. JellyFun did and does. Every tool decision is personal.
I can count among my friends and family some 50 Fire Sticks, and we're all happy with them, as they do what they say on the box.
We Tech folks (and some more than others) live in a bubble, but the other 99% of the users couldn't care less about this.
Because those folks don't move the needle on sales. They're buying one, maybe two firesticks and using them OOB. I'd bet a significant portion of sales go to people 'jailbreaking' them and buying in bulk.
Then this would be stupid. Obviously if the product stops doing what people want (jailbreaking, not sure what the scare quotes mean) sales will plummet.
> Even something as simple as alt-tabbing lagged for seconds on an overpowered machine.
This may not be KDE's fault; I tracked these kinds of issues down to some bad tunable defaults.
I came up with this:
----
cat /etc/sysctl.d/50-usb-responsiveness.conf
#
# Attempt to keep large USB transfers from locking the system (kswapd0)
#
vm.swappiness = 1
vm.dirty_background_ratio = 5
vm.dirty_ratio = 5
vm.extfrag_threshold = 1000
vm.compaction_proactiveness = 0
vm.vfs_cache_pressure = 200
# FIXME? 64K too big?
vm.page-cluster = 16
----
I have fast everything, NVMe SSD onboard and others in Thunderbolt 4 enclosures and 32GB of RAM on my 12th-Gen i7 with 20 (6+14) cores; there should have been no reason for any stuttering and/or Alt-Tab slowness while doing large file copies and finally got fed up, did some research and experimentation and use the above and it's not happened since.
YMMV, but it's worth a try.
(Oh, and on-topic, I've had to try Wayland (vs. X11) on my KDE desktop 'cause it seems to handle switching monitors when I go from home to work better; jury's still out if I'm keeping it)
You really only need dirty_ratio/bytes and dirty_background_ratio/bytes set to something lower than default. It also makes your progress bars show values closer to reality, especially when copying from fast to slow media.
Some distros already do set lower defaults, e.g. pop os:
> You really only need dirty_ratio/bytes and dirty_background_ratio/bytes set to something lower than default.
The vm.swappiness=1 was very necessary for me as well, and made as much difference as the dirties you'd mentioned.
I usually run Linus' master kernels (as I look for regressions in certain subsystems) and I know there's been some recent changes to the MM subsystem so this may explain some of the necessity for me.
I love(d) it and used it every time I'd go to WF, but TBF I heard about it by "accident" (some small ad somewhere, or maybe it was in the Amazon app?) ... I got the impression Amazon just didn't want to push it much.
Aw ... it was really nice at Whole Paycheck, I'm going to miss it.
Any guesses as to why? Unlike Google Maps Timeline data being subpoenaed, I can't see what LE could use with this (since they have other ways to determine you were at a store), so that can't(?) be the reason why.
https://www.imdb.com/title/tt0064177
It may be sick, but someone's got a sense of humor over there :)
reply