| commit | 06e44f94e019e5bfdab25652c06a2e90ec0d0905 | [log] [tgz] |
|---|---|---|
| author | Anand Ravi <[email protected]> | Wed May 28 20:15:03 2025 |
| committer | Chromium LUCI CQ <[email protected]> | Wed May 28 20:15:03 2025 |
| tree | e0ce04e17822a3262f6684b7eb3ba3512454a3dc | |
| parent | 28a00143aa45c26819a53069d0516360fad3fc2c [diff] |
Move background thread pool experiment to synthetic trial Currently, the experiment to study the effect of background thread pool on Android with and without priority inheritance locks uses server-side field trials but upon review of the field data the field trials are set up too late to take effect on the thread pool and the locks of interest. For this, we repurpose an existing, inactive background thread pool synthetic trial for the current experiment with a few modifications which allows us to drive the synthetic field trial from a server-side field trial using CachedFlags at the Java layer. The synthetic field trial is also split into two mutually exclusive trials to mimic the current faulty server-side field trial such that only those clients whose kernels support priority inheritance futexes are eligible for the priority inheritance supported synthetic field trial. The core idea behind this is that it allows us to study the effects of priority inheritance locks separately from background thread pools. Bug: 384902323 Change-Id: I184e23dd443b54851ec62b0eed3116b782d597af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6507144 Reviewed-by: Tom Sepez <[email protected]> Reviewed-by: Alex Moshchuk <[email protected]> Commit-Queue: Anand Ravi <[email protected]> Reviewed-by: Benoit Lize <[email protected]> Reviewed-by: Colin Blundell <[email protected]> Cr-Commit-Position: refs/heads/main@{#1466681}
ChromiumChromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.