Public bug reported:
Currently flash-kernel takes at least 1 and a half minutes (on fast SSD
storage) to execute on a Raspberry Pi. This is partly because a
considerable number of files are transferred compared to other platforms
(all supported dtbs, and their overlays, along with the kernel and
initrd which totals several hundred copy operations in all). However, a
large part of this is that "maybe_defrag" is called at the end of
"backup_and_install".
The "maybe_defrag" function checks the f-k database for the "Bootloader-
Has-Broken-Ext4-Extent-Support" flag to determine whether a
defragmentation run is required (it's not on Pi models). Unfortunately,
it checks this *every time* and the check is fairly expensive (involves
bash parsing the f-k database). If this value is cached (as many other
values from the database are), this reduces the overall f-k runtime to
~22 seconds (again, on fast SSD storage).
** Affects: flash-kernel (Ubuntu)
Importance: Undecided
Assignee: Dave Jones (waveform)
Status: New
** Changed in: flash-kernel (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: flash-kernel (Ubuntu)
Milestone: None => ubuntu-22.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965129
Title:
flash-kernel is extremely slow on raspi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1965129/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
