Description
Kitty seems to have a really slow start up on some systems, where as it is unaffected by this on others,
does not appear to be related to slow hardware.
I have a salvaged two core Baytrail system. that pulls acceptable start up time.
The system that I experience this under however runs the following:
Z170-A
I7-6700K
GTX 1050
Arch Linux - 4.18.4
I3-gaps - 4.150
Closed source NVIDIA drivers. - 396.54-2
I figured I'd be notable that I'm also running the Intel firmware init.
Now the unaffected system mirrors this software configuration except for the fact that it runs an integrated CPU and thus utilizes the mesa drivers instead of the NVIDIA ones.
Utilizing the -1
parameter bypasses the slow start up, as it hooks into an existing process.
Testing was conducted via executing time kitty fish -c exit:
with a potential -1
I default to the fish shell, but replacing it with sh or zsh has identical timing.
Unaffected Baytrail system timings.
Normal
0.38user 0.10system 0:00.53elapsed 93%CPU
0inputs+136outputs (0major+7867minor)pagefaults 0swaps
-1
0.22user 0.02system 0:00.25elapsed 98%CPU
0inputs+0outputs (0major+2244minor)pagefaults 0swaps
Now the affected system
Normal
0.15user 0.04system 0:01.63elapsed 12%CPU (0avgtext+0avgdata 51816maxresident)k
0inputs+8outputs (0major+9193minor)pagefaults 0swaps
-1
0.05user 0.00system 0:00.06elapsed 98%CPU (0avgtext+0avgdata 17768maxresident)k
0inputs+0outputs (0major+2253minor)pagefaults 0swaps
It seems that CPU utilization is throwing some kind of wrench in the loop, but I cannot say.