Usage of swiftshader_indirect for GMD on GitHub Actions

[eygraber]

I see that the NightlyBaselineProfiles sets

android.testoptions.manageddevices.emulator.gpu="swiftshader_indirect"

even though hardware acceleration is used.

Are there still performance benefits to using swiftshader_indirect?

[yschimke]

It's also still the guidance on android-emulator-runner https://github.com/ReactiveCircus/android-emulator-runner/blob/main/README.md

[eygraber]

It wasn't clear to me if that was something they needed to update, or if it's still valid - ReactiveCircus/android-emulator-runner#419

[yschimke]

Relevant discussion on https://issuetracker.google.com/issues/287312019

[eygraber]

What's confusing me is that the reply to this comment (yours?) from that issue says to use swiftshader_indirect, but the docs seem to indicate that host will perform the best if hardware acceleration is available.

swiftshader_indirect: Use a Quick Boot-compatible variant of SwiftShader to render graphics using software acceleration. This option is a good alternative to host mode if your computer can't use hardware acceleration.

[yschimke]

Maybe worth a reply on that issue?

[alamryaqdh-sketch]

I see that the NightlyBaselineProfiles sets

android.testoptions.manageddevices.emulator.gpu="swiftshader_indirect"

even though hardware acceleration is used.

Are there still performance benefits to using swiftshader_indirect?