When running xk6-browser even when no requests are being made the Console Windows Host process is taking 17-18% CPU constantly. This seem to be a serious overhead and kind of prevents me from running the test on the local machine I want to test.
Is there any way to get rid of that overhead, it feels like spin locking?
For comparison the actual K6 process is at 0.8%.
Thanks for reporting this issue.
We will try to reproduce the problem on our side. Could you provide us with the following details:
- Windows OS version
- Chrome browser version
- xk6-browser version
- Your system specs
- Steps you’ve taken when measuring this problem.
- Your script, if possible.
Hi, the -q flag brings the CPU load to 0. So it seems you are a bit to eager to update the console.
|OS Name|Microsoft Windows 10 Enterprise|
|Version|10.0.19043 Build 19043|
|Processor|11th Gen Intel(R) Core™ i7-1185G7 @ 3.00GHz, 1805 Mhz, 4 Core(s), 8 Logical |Total Physical Memory|31,7 GB|
|Available Physical Memory|16,1 GB|
|Total Virtual Memory|36,5 GB|
|Available Virtual Memory|15,1 GB|
|Page File Space|4,75 GB|
Steps taken: Basically opening taskmanager and then starting the script.
I can replicated it with any simple “make request and wait a few seconds” script.
Thanks for the detailed information.
It seems you’re using an older version of xk6-browser. It would be great if you could upgrade to the latest version and try again to see if anything changes?
It’s helpful to see the
-q flag changes the scenery. We will focus on there.
PS: I created an issue to track this, here.