Confirmed users
42
edits
Project Dory: Difference between revisions
m
minor updates
m (Add test summary) |
m (minor updates) |
||
| Line 4: | Line 4: | ||
** Clean up preferences (unused, incorrectly used, non-obvious). | ** Clean up preferences (unused, incorrectly used, non-obvious). | ||
* Use preferences as performance tuning knobs and investigate the performance implications of these knobs. | * Use preferences as performance tuning knobs and investigate the performance implications of these knobs. | ||
** | ** Categorize the preferences w.r.t their relevance to performance. | ||
** Tweak the preferences and run automated tests against the values to see their performance implications. | ** Tweak the preferences and run automated tests against the values to see their performance implications. | ||
| Line 17: | Line 17: | ||
== Roadmap == | == Roadmap == | ||
* Find a systematic way to manage and | * Find a systematic way to manage and categorize default preferences. | ||
** Co-work with libpref redesign project on | ** Co-work with libpref redesign project on how default preferences are populated in the system. | ||
** Find performance related preferences during the process. | ** Find performance related preferences during the process. | ||
** Get feedback from relevant teams. | ** Get feedback from relevant teams. | ||
*** Initially we may target JS related preferences. | *** Initially we may target JS related preferences. | ||
** | ** Find a way to record the performance implications along with other metadata for prefs. | ||
== Things to Consider == | == Things to Consider == | ||
* | * The current pref format is likely to remain for backward compatibility, at least for user-modified prefs. | ||
** Given that, how do we add new semantics to prefs and also maintain backward compatibility? | |||
*** Record the new semantics "out-of-band", like use a separate json file to record the new semantics for prefs. | |||
* What data should a pref contain? | * What data should a pref contain? | ||
** Internal name, a more descriptive name, description, default value, etc. | ** Internal name, a more descriptive name, description, default value, etc. | ||
| Line 84: | Line 86: | ||
** network.http.spdy.chunk-size: there is no noteworthy performance difference in using non-default values. | ** network.http.spdy.chunk-size: there is no noteworthy performance difference in using non-default values. | ||
** network.predictor.preconnect-min-confidence: there is no noteworthy performance difference in using non-default values. The only exception is test case 'test_firefox_gsheet_ail_clicktab_0'. More tests against is is on the fly. Results to be updated. | ** network.predictor.preconnect-min-confidence: there is no noteworthy performance difference in using non-default values. The only exception is test case 'test_firefox_gsheet_ail_clicktab_0'. More tests against is is on the fly. Results to be updated. | ||
** layout.display-list.retain | ** layout.display-list.retain: TBD | ||
** network.tcp.sendbuffer: for most test cases, there is no noteworthy performance difference in using non-default values. The only exception is 'test_firefox_gsheet_ail_clicktab_0', where 65536 performs better than the default. | ** network.tcp.sendbuffer: for most test cases, there is no noteworthy performance difference in using non-default values. The only exception is 'test_firefox_gsheet_ail_clicktab_0', where 65536 performs better than the default. | ||
** network.http.speculative-parallel-limit: for most test cases, there is no noteworthy performance difference in using non-default values. The only exception is 'test_firefox_gsheet_ail_clicktab_0', where the default value (6) performs worse than the other 2 values under test. | ** network.http.speculative-parallel-limit: for most test cases, there is no noteworthy performance difference in using non-default values. The only exception is 'test_firefox_gsheet_ail_clicktab_0', where the default value (6) performs worse than the other 2 values under test. | ||
** network.http.spdy.default-concurrent: for most test cases, there is no noteworthy performance difference in using non-default values. The only exception is 'test_firefox_gsheet_ail_clicktab_0', but the default value has contradictory results in mean and median compared to the other 2 tested values. | ** network.http.spdy.default-concurrent: for most test cases, there is no noteworthy performance difference in using non-default values. The only exception is 'test_firefox_gsheet_ail_clicktab_0', but the default value has contradictory results in mean and median compared to the other 2 tested values. | ||
** network.http.max-persistent-connections-per-server: for most test cases, there is no noteworthy performance difference in using non-default values. The only exception is 'test_firefox_gsheet_ail_clicktab_0', where 1 performs better than the default. | ** network.http.max-persistent-connections-per-server: for most test cases, there is no noteworthy performance difference in using non-default values. The only exception is 'test_firefox_gsheet_ail_clicktab_0', where 1 performs better than the default. | ||
== Bugs == | |||
* Meta bug 1188411 and dependent bugs. | |||
== External Links == | == External Links == | ||