| commit | 6408ebdcd5ea380c34079856a1beedcd69952c63 | [log] [tgz] |
|---|---|---|
| author | Joe Mason <joenotcharles@google.com> | Thu Nov 30 17:13:50 2023 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Nov 30 17:13:50 2023 |
| tree | 65d81cd3f6ddfa4e3608a7ada9b8019050381da9 | |
| parent | 7d699fbcb7f6f2974eee5e8771f2939ac67321d1 [diff] |
Implement ResourceAttribution kMemorySummary queries * Adds a MemoryMeasurementProvider owned by QueryScheduler. QueryScheduler::RequestResults now invokes one or both of CPUMeasurementMonitor and MemoryMeasurementProvider, depending on the resource types in the request, and passes the results to a BarrierCallback that invokes the final result callback once all providers have returned results. * Wraps the output of both CPUMeasurementMonitor and MemoryMeasurementProvider in a QueryResult variant so both results can be passed to the same QueryScheduler callback. * Adds a FakeMemoryMeasurementDelegate for testing, and moves it and the existing CPU delegate to measurement_delegates.h. * Plumbs through SetDelegateFactoryForTesting to set the MemoryMeasurementDelegate on QueryScheduler's MemoryMeasurementProvider. * Adds more compute gMock matchers, with better error output, to gtest_util.h. * Cleanup to keep CPUMeasurementMonitor consistent with MemoryMeasurementProvider: removes redundant `cpu_measurement` prefix from delegate-related members. * Cleanup: removes unused CallbackQueryResultObserver from query_scheduler_unittest.cc. Bug: 1471683 Change-Id: I018a539dc5c1587479f413cafbade3a59a0edff2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5069934 Reviewed-by: Patrick Monette <pmonette@chromium.org> Commit-Queue: Joe Mason <joenotcharles@google.com> Cr-Commit-Position: refs/heads/main@{#1231362}
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.