@@ -53,18 +53,18 @@ By default it exposes the `public` dir using the `1234` port.
5353$ go run ws/main.go
5454```
5555
56- ## Single request
57-
58- This bench is a very basic test to compare the two software.
59- We start the browser and request the fake web page once with full JS execution. The final DOMTree is
60- rendered in stdout.
61-
6256### Test machine
6357
6458The tests are run in an AWS m5.large (x86_64) with a fresh Debian install.
6559
6660![ aws.m5 neofetch] ( ./img/aws_m5_neofetch.png )
6761
62+ ## Single request
63+
64+ This bench is a very basic test to compare the two software.
65+ We start the browser and request the fake web page once with full JS execution. The final DOMTree is
66+ rendered in stdout.
67+
6868We use Google Chrome version 122.0.6261.94.
6969
7070``` console
@@ -162,22 +162,10 @@ dependencies, mainly Playwright.
162162You have also to install [ Google Chrome] ( https://www.google.com/chrome/ ) and
163163Lightpanda browser, but the code is not publicly available yet.
164164
165- ### Demo web page
166-
167- Same as previously, the benchmark assumes the demo page is running on the host.
168- If you already have [ Go] ( https://go.dev/dl ) , you can use direcly the npm script
169- with ` npm run ws ` .
170-
171- ### Test machine
172-
173- The tests are run in an AWS m5.large (x86_64) with a fresh Debian install.
174-
175- ![ aws.m5 neofetch] ( ./img/aws_m5_neofetch.png )
165+ ### Google Chrome benchmark
176166
177167We use Google Chrome version 123.0.6312.105.
178168
179- ### Chrome benchmark
180-
181169The ` playwright/chrome.js ` benchmark accepts multiple env vars to be configured.
182170* ` CHROME_PATH ` is the path to your Google Chrome bin,
183171* ` BASE_URL ` is the base url of the running web reser to request, by default ` http://127.0.0.1:1234 ` ,
0 commit comments