1390765 - Rename the memory/gc related prefs to all have the same prefix

Status: NEW

(Core :: JavaScript: GC, enhancement, P4)

Description

[Paul Bone [:pbone]]

Currently some of the javascript memory/gc preferences have different prefixes, they should have the same prefixes unless compatibility may be an issue.

Some prefixes currently have "mem.gc" in them redundantly.  I suggest the prefix should be:

    javascript.options.mem.

It can include gc and other memory things.

Comment 1

[Paul Bone [:pbone]]

Steve suggested this, I would like to know is renaming the prefs a problem for backwards compatibility?  How should it be handled?

Comment 2

[Jon Coppeard (:jonco)]

This will end up resetting the pref for any users who have changed one of these in their profile.  I don't think this is a big deal in this case (the default GC settings should work well for everyone).  But I don't actually know, so...

Smaug, do we have any guidelines around renaming prefs?

Comment 3

[Olli Pettay [:smaug][[e-mail]]]

I don't have. But aren't the prefs rather experimental or such, so I don't think we need to provide particular "API stability" there.

Comment 4

[Jon Coppeard (:jonco)]

(In reply to Olli Pettay [:smaug] from comment #3)
Great, let's do this.

Comment 5

[Paul Bone [:pbone]]

Why not add a new pref that gets used in these situations, like we do for when a GC is running on different zones.  It'll still break anyone's configuration but it'll be tunable/documented.  Maybe I'm getting too pref-happy?

Comment 6

[Paul Bone [:pbone]]

(In reply to Paul Bone [:pbone] from comment #5)
> Why not add a new pref that gets used in these situations, like we do for
> when a GC is running on different zones.  It'll still break anyone's
> configuration but it'll be tunable/documented.  Maybe I'm getting too
> pref-happy?

Disregard this comment (I don't seem to be able to delete it), I thought we were talking about something else.