We would like to investigate investigate the impact of allocating more memory in Chrome renderer process on Android.
We would like to investigate investigate the impact of allocating more memory in Chrome renderer process on Android. The doucment about this finch experiment is: https://docs.google.com/document/d/1LBHWM35rVCXsmHj0-_KKxZqiPWcSPh7dMAKWcEG0uwQ/edit?usp=sharing
Then lets assign an owner :)
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/502a8d5ecd0c1df7e38ca7fd37da126cb99f5585 commit 502a8d5ecd0c1df7e38ca7fd37da126cb99f5585 Author: Takashi SAKAMOTO <tasak@google.com> Date: Wed May 23 15:26:08 2018 Move MemoryAblationExperiment from chrome/browser/experiments to third_party/blink/(public/)common We need to use MemoryAblationExperiment from browser to common, because we are planning to do MemoryAblationExperiment for renderers. We will add a code invoking MemoryAblationExperiment for renderers (i.e. MemoryAblatinExperiment::MaybeStartForRenderer or something) in another patch. Change-Id: Ib786c87f0b300a8613b1b1d8e851fdaedacc6fb8 Bug: 845371 Reviewed-on: https://chromium-review.googlesource.com/1065561 Commit-Queue: Kentaro Hara <haraken@chromium.org> Reviewed-by: Jochen Eisinger <jochen@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#561094} [modify] https://crrev.com/502a8d5ecd0c1df7e38ca7fd37da126cb99f5585/chrome/browser/BUILD.gn [modify] https://crrev.com/502a8d5ecd0c1df7e38ca7fd37da126cb99f5585/chrome/browser/about_flags.cc [modify] https://crrev.com/502a8d5ecd0c1df7e38ca7fd37da126cb99f5585/chrome/browser/chrome_browser_main.cc [modify] https://crrev.com/502a8d5ecd0c1df7e38ca7fd37da126cb99f5585/third_party/blink/common/BUILD.gn [rename] https://crrev.com/502a8d5ecd0c1df7e38ca7fd37da126cb99f5585/third_party/blink/common/experiments/memory_ablation_experiment.cc [modify] https://crrev.com/502a8d5ecd0c1df7e38ca7fd37da126cb99f5585/third_party/blink/public/common/BUILD.gn [rename] https://crrev.com/502a8d5ecd0c1df7e38ca7fd37da126cb99f5585/third_party/blink/public/common/experiments/memory_ablation_experiment.h
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/91c27a2c3e92921c24ef18cffd8e190791ebb661 commit 91c27a2c3e92921c24ef18cffd8e190791ebb661 Author: Takashi SAKAMOTO <tasak@google.com> Date: Thu May 24 11:43:16 2018 Add RendererMemoryAblation features for renderer memory ablation experiment. Bug: 845371 Change-Id: I6ccd560af4739f472035b6ff357346e7d6cc4cf8 Reviewed-on: https://chromium-review.googlesource.com/1071048 Commit-Queue: Takashi Sakamoto <tasak@google.com> Reviewed-by: Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#561465} [modify] https://crrev.com/91c27a2c3e92921c24ef18cffd8e190791ebb661/third_party/blink/common/experiments/memory_ablation_experiment.cc [modify] https://crrev.com/91c27a2c3e92921c24ef18cffd8e190791ebb661/third_party/blink/public/common/experiments/memory_ablation_experiment.h [modify] https://crrev.com/91c27a2c3e92921c24ef18cffd8e190791ebb661/third_party/blink/renderer/controller/blink_initializer.cc
Comment 1 by mlippautz@chromium.org
, May 22 2018Status: Assigned (was: Untriaged)