[SessionStorage] Optimizing opening & forking of empty storage areas.
There are still a large number of renderer hangs from GetAll. Since the other possible hang call sites have been marked [Sync], this means that the loading of the storage area map is the final obvious area where this hang could be occurring. mek@ and I found a number of possible optimization spots where a map is known to be empty during the GetAll (or Fork) calls, and in these cases the code can avoid hitting disk. Hopefully this captures many common cases and can help the code hit disk less. https://docs.google.com/document/d/1Pw8W74-7NCHpxrtglVHqFZpLV_p2JFwdMNqo03kx2l8/edit has the discussion notes. R=mek@chromium.org Bug: 897581 Change-Id: I92de5848ebf17e2ab4fd5cd85610922858e629a8 Reviewed-on: https://chromium-review.googlesource.com/c/1488178 Commit-Queue: Daniel Murphy <dmurph@chromium.org> Reviewed-by:Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/master@{#635790}
Showing
Please register or sign in to comment