Feature #6877

Research how the check for upgrades could require less RAM

Added by intrigeri 2014-03-07 12:09:30 . Updated 2019-04-07 09:19:03 .

Status:
Rejected
Priority:
Low
Assignee:
Category:
Target version:
Start date:
2014-03-07
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
0
Affected tool:
Upgrader
Deliverable for:

Description

It might be that the initial check for available memory (in the shell wrapper) uses overly conservative settings. Otherwise, porting the whole things from Moose to Moo (doable on Wheezy) or Moops (doable on Jessie, with a couple backports) might help.

Subtasks

Related issues

Related to Tails - Feature #6876: Have the incremental upgrade process use less RAM Resolved
Related to Tails - Feature #10115: Add a splash screen to Tails persistence assistant Rejected 2015-08-28

History

#1 Updated by intrigeri 2015-03-16 22:34:06

  • Description updated

#2 Updated by intrigeri 2015-08-15 08:34:08

Memory::Usage is now in sid, which should help.

#3 Updated by intrigeri 2015-08-28 10:52:10

  • related to Feature #10115: Add a splash screen to Tails persistence assistant added

#4 Updated by intrigeri 2018-08-18 08:54:42

I’ve successfully ported tails-persistence-setup from Moose to Moo + Function::Parameters. It would be good to measure how it affected its RAM consumption (Tails 3.8 vs. 3.9) and if it makes a relevant difference, then I should consider porting the Upgrader as well.

#5 Updated by Anonymous 2018-08-19 06:08:49

  • Priority changed from Low to Normal

Somebody seems to be working on this → setting priority to normal.

#6 Updated by intrigeri 2018-08-19 08:22:36

  • Priority changed from Normal to Low

#7 Updated by intrigeri 2019-04-07 09:19:03

  • Status changed from Confirmed to Rejected
  • Assignee deleted (intrigeri)

Given we’d like to replace our Upgrader with a better, non-NIH solution, I don’t think that it’s a good use of our time to port it to a new set of dependencies now.