Skip to content

[Dev]Identify _wait_for_stable_network as Performance Bottleneck #6

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

HongxiaoN
Copy link
Collaborator

Pull Request: Identify _wait_for_stable_network as Performance Bottleneck

Summary

Instrumented per-step timing logs in

_wait_for_page_and_frames_load
  • Instrumented per-step timing around _wait_for_stable_network
  • Observed repeated hits of full maximum_wait_page_load_time (20s) on nearly every step
  • Noted other stages (_check_and_handle_navigation, asyncio.sleep, _update_state) take <1s each
  • Concluded that the custom network‐idle wait is the dominant contributor (>80%) to end‐to‐end latency

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

Successfully merging this pull request may close these issues.

1 participant