716324 - File and prioritize Memshrink bugs in PSM and in NSS as used by Gecko/Firefox

Status: RESOLVED WONTFIX

(Core :: Security: PSM, defect, P3)

Description

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

+++ This bug was initially created as a clone of Bug #716323 +++

In bug 576902 comment 9, njn wrote:
> > AFAICT, this bug is over-prioritized for the Memshrink effort. For
> > Firefox, we are almost definitely better off working on other
> > things in Necko/PSM for Memshrink. My patch only saves 18KB of
> > memory per SSL connection.
>
> Which Necko/PSM things are more important?  How many SSL connections
> do we typically have at any one time?

This bug is about providing Nicholas an answer to that question. We (Necko team) should document what things we can do within Necko to reduce memory, and work with the performance team to prioritize them. File bugs, set the priority (P1, P2, etc.) for the Necko team, and estimate a priority for the performance team (status whiteboard: [Memshrink-P1], [Memshrink-P2]). (These priorities might not match.)

FWIW, I have some vague ideas here but I am not sure when I will have time to work on this.

Comment 1

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

s/Necko/PSM/ above.

Comment 2

[Nicholas Nethercote [inactive]]

We decided in the MemShrink meeting that this bug doesn't need the MemShrink tag, but any bugs filed as a result of this can have the MemShrink tag.

BTW, in all my memory profiling of Firefox I haven't seen NSS/PSM stuff show up high.

Comment 3

[Dana Keeler (she/her) (use needinfo) [:keeler]]

Sounds like this isn't actively being worked on and isn't much of a priority.