Applied to:
- kinetic/linux:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next&id=04f71532747e18d2f7cb57f0d3cb66f6c00f3b24
- linux-unstable:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/unstable/commit/?id=b7efb6d15dea641b6944b245864e1e618c275aaa
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1980861
Title:
Please enable CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU
Status in Snappy:
New
Status in linux package in Ubuntu:
Fix Committed
Bug description:
The snapd/desktop/advocacy team are investigating the startup
performance of running snaps.
While doing this and comparing various distros (fedora, opensuse,
ubuntu) on Igors reference hardware we noticed that fedora is
substantially faster at starting snaps.
After some research it turns out that they use the
CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU=y option when we use
CONFIG_SQUASHFS_DECOMP_SINGLE.
I build^Whacked a test kernel in my ppa:mvo/tmp PPA that just changes
this one option (https://paste.ubuntu.com/p/NvS4GQjnSp/) and with that
the first run firefox startup went from 15s to 6s (!) on Igors
reference hardware. Given the dramatic performance improvements we
would like to get this option switched.
However we need to be careful and double check that the results from
https://bugs.launchpad.net/snappy/+bug/1636847 are no longer an issue
- back in 2016 the kernel team swtich to _DECOMP_SINGLE because just
mounting a snap would use up 131Mb or memory(!).
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1980861/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
