commit | da579410e4fbb9150d69e131843274b45bfe1810 | [log] [tgz] |
---|---|---|
author | Balazs Engedy <engedy@chromium.org> | Tue Aug 06 14:16:56 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Aug 06 14:16:56 2019 |
tree | e92a28d13a88f4f18bb9962fb51f8cbbd3595ac0 | |
parent | b81879765390d27768a7b459152d0f6bf86a302b [diff] |
Revert "Reland "CacheStorage: Allow reads to be executed in parallel."" This reverts commit 1d54425457da7615e23835c19f569bf086db3e7e. Reason for revert: Causes virtual/cache-storage-parallel/external/wpt/service-workers/service-worker/interfaces-sw.https.html to time out on Linux MSAN. Original change's description: > Reland "CacheStorage: Allow reads to be executed in parallel." > > This is a reland of cca6943d4d6b44265e9904104164fd7e4bde42aa > > Original change's description: > > CacheStorage: Allow reads to be executed in parallel. > > > > This CL adds the CacheStorageParallelOps feature with the associated > > "max_shared_ops" parameter. Enabling the feature and setting the > > parameter to greater than one will allow read-only cache_storage > > operations to run in parallel. By default parallel operation is > > disabled. > > > > The overall design is to treat each CacheStorageScheduler as if it > > has its own read-write-lock. When an operation is scheduled it must > > be flagged as either "shared" or "exclusive". Some number of shared > > operations (determined by the feature param) may run in parallel. > > Exclusive operations always run by themselves without parallelism. > > > > This CL also includes the ServiceWorkerCache.PeakParallelSharedOps > > histogram which will measure how much parallelism we actually see in > > practice. The peak is measured across a small time period defined by > > when an idle scheduler begins running its first shared op to until it > > stops running all shared ops. > > > > Bug: 985379 > > Change-Id: I4e318b719b51da079ff584acd1fb398d898660d7 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1709008 > > Reviewed-by: Jesse Doherty <jwd@chromium.org> > > Reviewed-by: Daniel Murphy <dmurph@chromium.org> > > Reviewed-by: John Abd-El-Malek <jam@chromium.org> > > Reviewed-by: Rayan Kanso <rayankans@chromium.org> > > Commit-Queue: Ben Kelly <wanderview@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#680986} > > TBR=jwd@chromium.org,dmurph@chromium.org,jam@chromium.org,rayankans@chromium.org > > Bug: 985379 > Change-Id: I83d8ce38a647b00e658dc1e2e17828468475cc66 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1737031 > Reviewed-by: Ben Kelly <wanderview@chromium.org> > Commit-Queue: Ben Kelly <wanderview@chromium.org> > Cr-Commit-Position: refs/heads/master@{#684049} TBR=dmurph@chromium.org,jwd@chromium.org,jam@chromium.org,rayankans@chromium.org,wanderview@chromium.org Change-Id: I879f85342779a56f445cb6a157aeb5d74fcd3771 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 985379 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1738591 Reviewed-by: Balazs Engedy <engedy@chromium.org> Commit-Queue: Balazs Engedy <engedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#684330}
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.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .