Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A noticeably worse performance (compared to gecko) when enabling passthrough in Pico 4 #112

Open
rafi16jan opened this issue Jul 28, 2024 · 3 comments

Comments

@rafi16jan
Copy link

When comparing latest gecko Wolvic to Wolvic chromium 0.9.1, browsing regular webpage is noticeably slower than the gecko version. What is probably the root cause of the issue?

@svillar
Copy link
Member

svillar commented Jul 30, 2024

I've also noticed that, we'd need to figure out because the web engine should not be affected by enabling passthrough

@jdagdelen
Copy link

Enabling passthrough may be lowering the CPU level on the system. I don't know exactly for Pico but it does that on Quest.

@rafi16jan
Copy link
Author

Enabling passthrough may be lowering the CPU level on the system. I don't know exactly for Pico but it does that on Quest.

Then why the gecko version not affected? Does gecko utilizes lower cpu usage?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants