Closed
Bug 1058962
Opened 11 years ago
Closed 9 years ago
Simulate places usage on a test machine to measure performance changes related to favicon size increase.
Categories
(Toolkit :: Places, defect)
Toolkit
Places
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: rittme, Assigned: rittme)
References
Details
Changing the maximum favicon size (bug 798223) can have some performance impacts on the database. To evaluate that, we can simulate browser usage using a test machine and make performance comparisons between profiles.
This tests should allow us to check for performance impacts from database fragmentation.
MattN suggested the following procedure on bug 798223:
1) Create a test places.sqlite DB using data from telemetry and choosing median values for bookmarks/history. For profile A have all favicons be 1KB and for profile B have them all b 5KB.
2) Delete X% of the places randomly
3) Insert a similar amount of new places
4) Repeat 2 & 3 some times
5) Compare the performance of profiles A and B (on the same computer with the same procedures above) using the existing telemetry plus new telemetry probes.
Flags: firefox-backlog?
Updated•11 years ago
|
Flags: qe-verify?
Flags: firefox-backlog?
Flags: firefox-backlog+
| Assignee | ||
Updated•11 years ago
|
Assignee: nobody → bernardo
Flags: qe-verify? → qe-verify-
Comment 1•11 years ago
|
||
Hi Bernardo, can you assign a point value for this bug.
Status: NEW → ASSIGNED
Iteration: --- → 35.1
Flags: needinfo?(bernardo)
| Assignee | ||
Updated•11 years ago
|
Points: --- → 5
Flags: needinfo?(bernardo)
| Assignee | ||
Updated•11 years ago
|
Points: 5 → 8
Updated•11 years ago
|
Iteration: 35.1 → 35.2
Updated•11 years ago
|
Iteration: 35.2 → ---
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•