On Friday December 23 2022 12:38:17 Patrick Nagel wrote:
>(probably 200-300ms of these "real" numbers is me reacting slowly to the
>window popping up and pressing ALT-F4...)
A thought: download the AppImage version of a larger application, like Firefox
on both systems, and do
```
> time /path/to/firefox*.AppImage --version
```
This will unpack the entire appimage contents to a temporary directory and
launch the application, excluding any KDE-specifics and also network activity
but above all the human reaction component. Should be a good test of your disk
subsystem.
NB: the `--version` trick works for KDE apps too of course:
```
> time dolphin5 --version
dolphin 20.07.70
1.074 user_cpu 0.257 kernel_cpu 0:04.02 total_time 32.8%CPU {46064M 898F 4110R
29529I 12O 840w 359c}
> time dolphin5 --version
dolphin 20.07.70
0.759 user_cpu 0.138 kernel_cpu 0:00.87 total_time 101.1%CPU {46068M 0F 4400R
3649I 4O 446w 167c}
> time kate5 --version
kate 19.08.3
0.920 user_cpu 0.249 kernel_cpu 0:02.73 total_time 42.4%CPU {45640M 380F 4320R
11687I 4O 775w 220c}
> time kate5 --version
kate 19.08.3
0.739 user_cpu 0.159 kernel_cpu 0:00.86 total_time 102.3%CPU {45488M 0F 4431R
3639I 4O 498w 185c}
```
Start up delays on my much slower system (that's an Intel N3150 CPU!) sometimes
*feel* like 20 seconds but clearly they're much less, so yeah, you may have an
issue somewhere. Have you checked your syslog and/or checked the SMART health
status of the drive in your slower system? Does the delay depend on how many
other applications you're running (i.e. how much free RAM you have)?
R.
