snapfuse use a lot of CPU inside containers when "core" and "snapd" is installed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Triaged
|
Medium
|
Michael Vogt |
Bug Description
When using the MAAS snap inside a LXD container, I notices that it was a lot
slower than usual. I noticed that snapfuse was often using 100% CPU.
You can reproduce this by installing the MAAS snap:
snap install maas --edge --devmode
Then run 'maas init', accepting the default options. During the
"Performing database migrations" step, you'll see that snapfuse
is doing a lot of work, slowing things down.
As a data point, I measured how long it took to run 'maas init'
on my laptop:
'snap install' inside a container: 60 seconds
'snap install' outside a container: 45 seconds
'snap try' inside a container: 45 seconds
Both the container and host are up-to-date bionic systems.
If it makes a difference, I use ZFS as the backing file system, both
on the system itself and for LXD.
tags: | added: maas |
description: | updated |
tags: | added: snap |
tags: | removed: snap |
Changed in snapd: | |
status: | Fix Committed → Fix Released |
Changed in snapd: | |
status: | Fix Released → Triaged |
summary: |
- snapfuse use a lot of CPU inside containers + snapfuse use a lot of CPU inside containers when "core" is installed |
summary: |
- snapfuse use a lot of CPU inside containers when "core" is installed + snapfuse use a lot of CPU inside containers when "core" and "snapd" is + installed |
Changed in snapd: | |
importance: | Undecided → Medium |
I see a similar behavior on a machine using btrfs for both host and containers