commit | 8a88135440e7321fbfa7a74246ebb8cccb54a4ff | [log] [tgz] |
---|---|---|
author | Bo Liu <boliu@chromium.org> | Wed Dec 06 01:33:54 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Dec 06 01:33:54 2023 |
tree | 7c2ba2c3ee8c13fbaa752d61add160256e164ac5 | |
parent | e7e70826834f7b5a395e8cd63d43a73967ca19b7 [diff] |
gpu: Prune old TransferCache entries Business logic changes: * Transfer cache will post hard-coded 30s delayed task to clear entries that are older than 30s * Transfer cache will only have one pending task, but keeps track of requests to post more tasks while one is pending and post again when the current pending task runs. This means old entry can live close to 60s at the longest end. * Pruning entries is similar to enforcing memory limits. * "Flush" after pruning at the end, which is implemented by scheduling GrCacheController to run (with up to 1s delay) * Change GrCacheController to flush for vulkan as well by flush (with a callback) and submit. Changes for experimentation: * Client side purge kPurgeOldCacheEntriesOnTimer moved to //gpu * Add new feature kPruneOldTransferCacheEntries * * If kPurgeOldCacheEntriesOnTimer is disabled, both client and service side logic are disabled * * Otherwise, kPruneOldTransferCacheEntries controls whether to use service- or client-side pruning * * This is to support hold back experiment for client side purge * Add kPruneOldTransferCacheEntries to webview flags * Enable kPruneOldTransferCacheEntries in fieldtrial_testing_config.json Bug: 1442988 Change-Id: Iea38803b57cb4089f7bdf3f4b00526019c757fcc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5074796 Commit-Queue: Bo Liu <boliu@chromium.org> Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org> Reviewed-by: Benoit Lize <lizeb@chromium.org> Reviewed-by: Thiabaud Engelbrecht <thiabaud@google.com> Cr-Commit-Position: refs/heads/main@{#1233700}
Chromium 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.