75
edits
Electrolysis/Meetings/2016-02-11: Difference between revisions
Jump to navigation
Jump to search
Electrolysis/Meetings/2016-02-11 (view source)
Revision as of 17:00, 11 February 2016
, 11 February 2016gabor's progress edit
(gabor's progress) |
(gabor's progress edit) |
||
| Line 14: | Line 14: | ||
* {{bug|1179735}} (p1 perf, - tp5o_scroll regression) - Not a lot of progress. It turns out my simulation was not correct, I should have disabled vsync, I'm trying again. | * {{bug|1179735}} (p1 perf, - tp5o_scroll regression) - Not a lot of progress. It turns out my simulation was not correct, I should have disabled vsync, I'm trying again. | ||
* {{bug|1182637}} (p1 perf, - e10s is jankier than non-e10s) - Closed the bug for now | * {{bug|1182637}} (p1 perf, - e10s is jankier than non-e10s) - Closed the bug for now | ||
* {{bug|1232638}} - (p1 perf, -IPDL::PCookieService::RecvGetCookieString causing janks) - I looked into the possible solutions, and it's a lot harder than I originally thought. The janks happening because reading the database for cookies is slow (maybe the other related operations as well with the strings), and there is no way to do that work off the main thread while we're blocking the content process (the request has to be sync) | * {{bug|1232638}} - (p1 perf, -IPDL::PCookieService::RecvGetCookieString causing janks) - I looked into the possible solutions, and it's a lot harder than I originally thought. The janks happening because reading the database for cookies is slow (maybe the other related operations as well with the strings), and there is no way to do that work off the main thread while we're blocking the content process (the request has to be sync) Looking at the data though, I still don't think this is P1, this issue is responsible for about 3% of the chrome process janks, while we don't know anything about almost 50% (pesudo stack). As it turns out the pseudo stack enhancing patch did not help... | ||
Looking at the data though, I still don't think this is P1, this issue is responsible for about 3% of the chrome process janks, while we don't know anything about almost 50% (pesudo stack). As it turns out the pseudo stack enhancing patch did not help... | |||
* some initial multiprocess project planning | * some initial multiprocess project planning | ||
* IPC learning | * IPC learning | ||
* questions: why do we want to turn off e10s for web extensions and themes? | * questions: why do we want to turn off e10s for web extensions and themes? | ||