Closed Bug 1280674 Opened 8 years ago Closed 8 years ago

[tracking] Performance validation of L20n

Categories

(L20n :: General, defect)

Product:
L20n
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: zbraniecki, Assigned: zbraniecki)

References

Details

(Whiteboard: [gecko-l20n])

User Story

In order to start switching Firefox to L20n we need to prove that L20n is at least on par performance/memory wise with DTD/StringBundle approach.

We need to get numbers that prove that A vs. B (where A is DTD+Properties and B is L20n) is on par.
We should be able to predict the tpaint hit once we *add* L20n on top of DTD/Properties and understand expected drop once we *remove* DTD/Properties from the tpaint startup path.
      No description provided.
Blocks: gecko-l20n
User Story: (updated)
Depends on: 1287162
No longer depends on: 1287162
Assignee: nobody → gandalf
Depends on: 1289530
Summary: Performance validation of L20n → [tracking] Performance validation of L20n
Depends on: 1289535
Mass change dependency tree for bug 1279002 into a whiteboard keyword.
No longer blocks: gecko-l20n
Whiteboard: [gecko-l20n]
We're done here for now.

If you want to know what we did, read https://wiki.mozilla.org/L20n/Firefox/Performance
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.