Google Git
Sign in
chromium / chromium / src / 4dc925d5c219a09d759c88a6154c78b85a713dbb
commit4dc925d5c219a09d759c88a6154c78b85a713dbb[log] [tgz]
authorCorey Tabaka <eieio@chromium.org>Tue Dec 13 22:44:23 2022
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Dec 13 22:44:23 2022
tree34aa96be3265e8fcda01faa302a64ed6bfbd230e
parent2eedde169e971c8ba1358bb38a3cc505a358e947 [diff]
Apply kCompositing thread type to Media thread on Fuchsia.

Improve media performance on heavily loaded Fuchsia devices by applying
kCompositing thread type to the Media thread. The exact parameters of
this thread type are customized per-product using Fuchsia's scheduler
role mechanism.

In the long term, we would like to align on new thread types and
priorities for the media thread and related pool threads, suggested in
https://crrev.com/c/chromium/src/+/3920078/comment/545232d3_7203c331/

However, we have a release blocking performance bug that is confirmed to
be addressed by this minimal, Fuchsia-only change. Landing this in the
interim unblocks the release and buys time to align on the longer term
solution.

Bug: 1174339
Bug: b/242564647
Change-Id: I1ad68f83c84e645386dd154c3d2f7f3e03ba1c7b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4103643
Reviewed-by: danakj <danakj@chromium.org>
Commit-Queue: Corey Tabaka <eieio@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1082773}
1 file changed
tree: 34aa96be3265e8fcda01faa302a64ed6bfbd230e
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. WATCHLISTS
README.md

Logo Chromium

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.