Closed Bug 1297524 Opened 8 years ago Closed 2 years ago

Investigate performance penalty of profile migration in Firefox snaps

Categories

(Release Engineering Graveyard :: Release Automation: Snap, defect, P3)

Product:
Release Engineering Graveyard
Component:
Release Automation: Snap
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rail, Unassigned)

References

(Blocks 1 open bug)

Details

Every time when users update their snaps, the user profile is copied over before the new version starts. This way it's easier to rollback.

It would be great to figure out the penalty of this procedure and what happens to the old profiles (do they live forever?)
Priority: -- → P3
Component: Release Automation: Other → Release Automation: Snap

The profile folders are now stored in $SNAP_USER_COMMON, which is shared across all revisions of the snap, so there is no copying involved when updating.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Product: Release Engineering → Release Engineering Graveyard
You need to log in before you can comment on or make changes to this bug.