Google Git
Sign in
chromium / chromium / src / 6060205ed9c87d913135a042de145d2bdc4da6d1
commit6060205ed9c87d913135a042de145d2bdc4da6d1[log] [tgz]
authorJoe Downing <joedow@google.com>Fri Jan 13 19:10:36 2023
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jan 13 19:10:36 2023
treeb224fde0be305c941797538ab0913c87c7b505ca
parent7574a24b7c39527f4e40f5bff8417ed8a5ec4011 [diff]
Increase thread count for 5K displays

This CL increases the number of threads set in the VP9 and AV1 SW
encoder wrappers when CRD is remoting a 5K display.

While VP9 benefited from the thread increase, AV1 required a small
config change to see a performance gain. The AOM team suggested using a
smaller superblock size to increase parallelism with the increase thread
count which solved the perf issue.
See https://crbug.com/aomedia/3363 for more info.

Results w/ a 5K display on a 128 core machine using 32 threads running
a scrolling text workload:
VP9_I420: +2 FPS
VP9_I444: ~0 FPS
AV1_I420: +4 FPS
AV1_I444: +3 FPS

Bug: b:217468304
Change-Id: Iacf7d44115ce0f8363e9f0df6788f542e74a362e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4165961
Commit-Queue: Joe Downing <joedow@chromium.org>
Quick-Run: Marco Paniconi <marpan@google.com>
Reviewed-by: Lambros Lambrou <lambroslambrou@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1092536}
2 files changed
tree: b224fde0be305c941797538ab0913c87c7b505ca
  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. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  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.