|
|
|
|
|
|
by firebot
26 days ago
|
|
|
I think the web page delayed loading is often server-side these days trying to detect bots. Especially with a dynamic IP.... You'll generally be fine after that first detection flags you as human. Also this seems to affect firefox moreso than some other browsers, but that's subjective. Also, if you're familiar with sysinternals suite for Windows there's a Linux equivalent to all the tools with nice GUIs. So you should be able to track down most process-caused performance issues fairly easily without knowing all the appropriate CLI commands. |
|
|
- dns cache configuration
- wlan power saving which is kind of aggressive since Linux has had some power management issues
It's really why I go for a minimal distro, debian with xfce. There's not many components, they're not "tuned", and I can just kinda research any issues myself and find what works. Usually there's some pretty big gaps (missing a whole component, wildly malfunctioning, high resource utilization) and then it's easy to figure out. There's not much code, or really hard scripts to understand. Just maybe enable debug on the service. Learn where the developers put diagnostics (about:support is a godsend). You get to architect your hardware's success and get a rock-solid system. But yeah, if it's weird it might be weird for a while, haha.
For my setup I think the last few lessons were like:
- use gamescope for X11 Wine/Proton (huge.)
- Firefox profile reset to fix hardware decoding (followed some good guides and some bad guides)
- to make changes use the same git tag as your distro so the deps are easily in-reach.
My favorite new discovery for debian in particular is their extensive functional docs. https://www.debian.org/doc/manuals/debian-reference/
absolutely adore this.