Description
🚀 Feature Request
Summary
playwright-python currently makes frequent calls to inspect.stack, which significantly impacts performance in certain use cases, such as web scraping with scrapy-playwright. This feature request proposes adding an option to disable stack inspections to improve execution speed when debugging information is not required.
Use case
Although Playwright is primarily designed for end-to-end testing, some projects leverage it for web scraping, where performance is a key concern. In my case, I am using scrapy-playwright, and profiling results from cProfile indicate that inspect.stack
calls contribute to roughly 25% of the total execution time, as illustrated in the following icicle and call graph:

As far as I can tell, these calls are primarily used for debugging and are not critical for normal execution.
Proposed solution
Introduce an environment variable (e.g.: PW_INSPECT_STACK) that allows users to disable stack inspections when debugging is not required. The default value would be 1 to preserve the current behavior.
Motivation
- Performance Boost: Reducing unnecessary function calls can significantly speed up Playwright for scraping-heavy applications.
- Flexibility: Users who require stack traces for debugging can leave the option enabled.
- Backward Compatibility: The default behavior remains unchanged, ensuring no disruption for existing users.
Activity
luisferreira93 commentedon Feb 20, 2025
+1
mxschmitt commentedon Mar 31, 2025
Do you have in comparison how much time the actual page.goto/click/fill etc's took? Lets say 1s in average with network resources around different origins and sometimes even iframes etc. This should be way larger and demonstrate that its not worth investing into that end (inspector.stack).
neoncube2 commentedon Apr 22, 2025
I think I might be affected by this, too.
In my case, I load a page, check to make sure that a certain amount of buttons are visible, then execute a few thousand
page.evaluate()
calls in a tight loop.Profiling results
Use case
I have a game written in JavaScript, and I'm using Pytorch to train an AI to play the game. I use Playwright to load the page and then play the game via JS calls:
await evaluate('doGameAction', action_index)
As an aside: Is
evaluate()
truly async? It seems like it uses a lot of CPU, and I'm guessing that internally it may involve a loop with a bunch ofwait()
calls to see if the browser has finished executing the JS code.Thanks! :)
neoncube2 commentedon Apr 28, 2025
I think I might have a fix for this that improves performance and doesn't require a special flag! :)
I'm currently running some tests, and if they're successful, I'll probably open a PR within the next few days, God willing.
neoncube2 commentedon Apr 30, 2025
I've opened two PRs to fix this:
SichangHe commentedon Jun 4, 2025
No joke. MASSIVE speed up here to be had. For my crawler, with playwright==1.52.0, ~200 browser tabs, my main Python process CPU stays ~100% and the asyncio event loop hangs constantly. With an aggressive monkey patch inspired by @neoncube2's PRs, CPU is around 30% and the event loop almost doesn't hang.
I attach the monkey patch I am using in case it can help anyone.
What I mean by the event loop hanging.
Assuming all the blocking code have been moved to other threads, but there are more tasks than the event loop can handle, it will still have tasks piled up into a backlog, meaning it may not wake up an IO-bound/time-sleep task even if the response is here or the time is up.
Specifically, I use
asyncio.sleep
not waking up a while after the specified time has passed to detect when the event loop hanged.Flamegraphs of my crawler before and after the monkey patch shows the time
inspect.stack
took went down from ~80% to negligible.This shows
inspect.getsourcefile
being the culprit.jl-martins commentedon Jun 4, 2025
I did a similar monkey patch a while back and got similar improvements. Massive speed up indeed.
Thanks for sharing, @SichangHe!
neoncube2 commentedon Jun 5, 2025
Thanks, @SichangHe!
:D
Let me see if I can integrate this into my PR! :)