Die Burgruine und das Castle!
Liebe Leserinnen und Leser!
Nachdem ich gesternn... eher heute früh einen neuen Artikel auf meinem alten Castle veröffentlichte dachte ich so bei mir, daß ich wohl beide Blogs weiter fortsetze, also WordPress und hier Plume. Beide Systeme haban ihre Vor- und Nachteile.
WordPress kann mit Plugins ziemlich erweitert werden und hat einen internen HTML-Editor, was mir hier bei Plume ziemlich fehlt.
Plume dagegen ist von Haus aus Teil vom Fediverse, während man bei WP hierfür ein extra Plugin benötigt. Das Problem bei WP ist jedoch wenn man es wie ich selbst hostet, daß man sich einfach um alles kümmern muß, auch Updates.
Mit Markdown komme ich inzwischen einigermaßen klar, da ich hier im SeaMonkey ein spezielles echtes AddOn (BBCodeXtra) installiert habe. Das integriert ein Menü für Markdown, so daß man sich die entsprechenden Befehle nicht alle merken muß!
Was mir bei beiden Systemen fehlt ist die Möglichkeit Smilies einfach eizufügen. Ich nehme an, daß es bei WordPress dafür ein Plugin gibt, hier bei Plume sieht das leider etwas schlecht aus. Leider gibt es wohl auch kein AddOn für SeaMonkey, nur mehrere "Webextensions" habe ich gefunden.
Einfacher bei Plume ist hier klar die Anbindung an das Fediverse, das Plugin für WP scheint mir noch leicht fehlerhaft zu sein!
Obwohl ich Dank meiner Schlaganfälle gesundheitlich etwas angeschlagen bin kann ich mich nicht mehr so wie Früher um das Schreiben kümmern, trotzdem werde ich beide Blogs weiter führen. Ich hab das meiner leider inzwischen verstorbenen Ex-Ehefrau versprochen und habe vor, dieses Versprechen auch einzuhalten in Gedenken an Andrea!
Mal sehen, ob mir was wegen der Smilies einfällt.
Liebe Grüße nun aus der Burgruine zu Augsburg
Mike, TmoWizard


Nanook
in reply to Dariusmiles2123 • •jokro
in reply to Dariusmiles2123 • • •IanTwenty
in reply to jokro • • •This is my thought too. Your screenshots don't show cpu freq. Everything can appear normal on other measures but if your cpu has throttled right back it'll run slow with no obvious cause. I have seen this on certain laptops when external peripherals are added/removed after waking from sleep. Sometimes forcing sleep/wake or a reboot will fix.
Use
lscpuat the cmdline or better yet install gnome extension 'system monitor next' and put the cpu freq graph in your top bar to watch it in realtime.extensions.gnome.org/extension…
system-monitor-next - GNOME Shell Extensions
extensions.gnome.orgsnailstone
in reply to Dariusmiles2123 • • •kumi
in reply to Dariusmiles2123 • • •Apart from what others said about power/throttling, I wonder if the filled up memory during the upgrade (or other memory-heavy use) pushes some central pages to swap and then they stay there after?
After the upgrade and you have plenty of free memory again you can force back everything to RAM by temporarily disabling swap:
To list swap devices, just run
swapon.Also switching to an X11 window manager can be quite a lot snappier than modern GNOME for older hardware. You could try Xfce, Cinnamon, MATE, or KDE with the X session.
If it's not throttling/thernals, I wouldn't be surprised if those two together is what made things worse after migrating dist.
If you've been swapping heavily over time you might also want to check disk health with
smartctland check that you don't have related errors indmesg.If you press tab in htop you can also see if there is high IO load going on.
atzanteol
in reply to kumi • • •kumi
in reply to atzanteol • • •Hence:
If it's like the last htop image should be no problem.
atzanteol
in reply to kumi • • •Turning off swap could make things much worse though. The system will have less memory for file caches.
I'd leave swap alone, just monitor for whether the system is paging frequently. "vmstat 3" should show if you're writing to swap frequently.
kumi
in reply to atzanteol • • •How so, given that we immediately re-enable the same swap device right after so that it's only off for a very brief moment? Let go 😀
Anecdotally, this maneuver can help tremendously tonrecover responsiveness in some cases. I guess the overall sitiation could be improved by tweaking
vm.swappiness.Nanook
in reply to kumi • •atzanteol
in reply to kumi • • •See that
buff/cachecolumn? That's memory being used by the system for caching. Files you you open and access get cached into memory as do inodes, filesystem objects, etc. If you run a "find / -type f" twice in a row the second one will be significantly faster because the first run cached a lot of objects into memory.By starving the system of memory all that will be flushed and you get more disk access doing things you're actually trying to do. Whereas things sitting in swap are there because they aren't currently needed.
By turning off swap and then back on again you're just forcing the system to drop all that cache which it will then attempt to reclaim space for and push things back out to swap.
I don't know what benefit you think you'll gain in the process.
mech
in reply to Dariusmiles2123 • • •I'd guess at overheating, or an error with the CPU's energy management.
First thing I'd do is look if there's a BIOS update available.
Then install lm-sensors (there's also a GUI frontend called psensor and a gnome shell extension) to show CPU temperature, and check if they're too high. If they aren't, you could set your CPU to always use max power and see if that fixes it, but it will reduce battery life.
Or try a different distro from a live USB and see if that makes a difference.
isgleas
in reply to Dariusmiles2123 • • •utopiah
in reply to Dariusmiles2123 • • •It's all just speculations, both what you suggested and what others said.
You are on the right path with your screenshots but you might not be measuring the right thing.
So, you need a (paper) notebook to record objectively (not your biased feeling assuming a pattern that might not exist) when it happens and for how long. Only from then can you backtrack to WHAT causes it. Sure you can have some hypothesis (update related, screen attach/detach, BIOS, RAM, etc) but that should NOT lead to your data acquisition.
So you htop is nice but AFAICT it's just about CPU and memory, it's not about e.g. IO so consider instead
iotop, in particular if one process is some indexing (e.g. locatedb). Theoretically if it's not CPU/memory (which you are saying it's not the case) then it basically just leaves IO, that can be again indexing, some heavy process that is bottlenecked on disk access, but can also be a bug, e.g. BT pairing/unpairing that happens faster than you can notice.Think of this as a fun investigation that leads you to better understanding of your setup, good luck.
Dariusmiles2123
in reply to utopiah • • •Yeah I guess you’re right, my last chance of solving the problem could be by creating a spreadsheet with as much data as possible on every occurrence..
I don’t think it would be a thrilling investigation though😅
What are IO and Iotop?
atzanteol
in reply to Dariusmiles2123 • • •Input / Output.
Reading and writing to disk, network, etc.
iotopshows will show applications writing and reading from disk. It's going to likely be pretty sporadic.What may be happening, and what others are suggesting, is that you're running out of memory (8gig isn't that much these days). When that happens the system starts writing memory to disk so it can free more. That's what you see with the "swap" usage. You can see a bit more about your memory usage with
free -m:Using swap space isn't necessarily bad. But reading/writing to it frequently can be a performance killer. You can monitor that with a command called
vmstat:The columns to pay attention to there are under the
---swap--header.siis "Swap In" andsois "Swap Out. Those are reads/writes to and from swap space. Seeing a little activity there is fine. It is typically pretty spikey. But if you're seeing lots of numbers there then it could just indicate that you're running low on memory and the OS needs to move things to and from disk frequently. While it's moving things to and from the disk the application trying to use that memory has to wait.Nanook
in reply to Dariusmiles2123 • •TechnoCat
in reply to Dariusmiles2123 • • •Dariusmiles2123
in reply to TechnoCat • • •I’ve never heard of btop but I can look at it👍
But wouldn’t it be weird for it to be temperature related when the computer was just started and unplugging/plugging the external screen solve the issue? This would make think it’s display related no?
TechnoCat
in reply to Dariusmiles2123 • • •TechnoCat
in reply to Dariusmiles2123 • • •I will share an issue I and others have with their laptop that presents just a bit differently (a single cpu pegged at 100% instead of all of them).
If i wake my laptop from sleep while it is plugged into an external monitor, I will have a single cpu pegged at 100% trying to handle endless acpi interrupts. I have to hibernate my machine and turn it back on to fix it. Alternatively I can unplug the monitor before waking from sleep to prevent it from happening. I just hibernate instead of sleeping now.