Project

General

Profile

Feature #15290

Reduce IUK size

Added by anonym over 1 year ago. Updated 3 months ago.

Status:
Confirmed
Priority:
Low
Assignee:
Category:
-
Target version:
Start date:
03/09/2016
Due date:
% Done:

5%

QA Check:
Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:
Upgrader

Description

This is about researching low-hanging fruits to reduce the size of our IUKs in order to be nicer to users with lower amounts of RAM (strictly less than 3GB) and users with not very fast Internet connection.


Subtasks

Bug #11211: Don't include files from /usr/share/mime in IUKs if their only modification is mtimeConfirmed

Feature #11345: Ship less unneeded cache/generated files in the ISO and IUKIn Progress


Related issues

Related to Tails - Feature #15281: Stack one single SquashFS diff when upgrading In Progress 03/07/2014
Related to Tails - Feature #15289: Make Tails Upgrader suggest a manual upgrade to decrease future IUK sizes Confirmed 02/05/2018

History

#1 Updated by anonym over 1 year ago

  • Target version set to 2018

#2 Updated by anonym over 1 year ago

  • Related to Feature #15281: Stack one single SquashFS diff when upgrading added

#3 Updated by anonym over 1 year ago

This is related to #15281 (1BigIUK) because of the larger IUKs. Once we have it it really seems worth at least picking the low-hanging fruit among size optimizations.

#4 Updated by intrigeri over 1 year ago

  • Description updated (diff)

#5 Updated by u 9 months ago

  • Related to Feature #15289: Make Tails Upgrader suggest a manual upgrade to decrease future IUK sizes added

#6 Updated by anonym 4 months ago

  • Target version changed from 2018 to 2019

#7 Updated by intrigeri 3 months ago

  • Blocked by Feature #15277: Update our survey of non-NIH system upgrade solutions added

#8 Updated by intrigeri 3 months ago

  • Blocked by deleted (Feature #15277: Update our survey of non-NIH system upgrade solutions)

#9 Updated by intrigeri 3 months ago

anonym wrote:

This is related to #15281 (1BigIUK) because of the larger IUKs. Once we have it it really seems worth at least picking the low-hanging fruit among size optimizations.

Yes, maybe… but the marginal benefit (relative to the total upgrade download time) brought by such optimizations will actually be lower once IUKs get bigger. So I guess it could be worth giving a quick try to the low-hanging fruits I've identified on the subtasks and check how much space (and thus download time) we would save, before even evaluating whether these tricks break anything we care about. Now, no big deal if we don't do it IMO.

Also available in: Atom PDF