Skip to content

Commit 8ff3912

Browse files
committed
playwright: add chrome result on aws m5
1 parent bec682f commit 8ff3912

File tree

2 files changed

+22
-1
lines changed

2 files changed

+22
-1
lines changed

README.md

Lines changed: 22 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -168,6 +168,14 @@ Same as previously, the benchmark assumes the demo page is running on the host.
168168
If you already have [Go](https://go.dev/dl), you can use direcly the npm script
169169
with `npm run ws`.
170170

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)
176+
177+
We use Google Chrome version 123.0.6312.105.
178+
171179
### Chrome benchmark
172180

173181
The `playwright/chrome.js` benchmark accepts multiple env vars to be configured.
@@ -178,6 +186,19 @@ The `playwright/chrome.js` benchmark accepts multiple env vars to be configured.
178186
`npm run bench-chrome` starts a playwright process, load a Google Chrome
179187
instance and load the page to extract data 100 times.
180188

181-
```
189+
```console
182190
$ CHROME_PATH=`which google-chrome` npm run bench-chrome
191+
192+
> [email protected] bench-chrome
193+
> node playwright/chrome.js
194+
195+
................................................................................
196+
....................
197+
total runs 100
198+
total duration (ms) 18792
199+
avg run duration (ms) 184
200+
min run duration (ms) 168
201+
max run duration (ms) 323
183202
```
203+
204+
![aws.m5 Playwright with Google Chrome](./img/aws_m5_playwright_chrome.png)

img/aws_m5_playwright_chrome.png

144 KB
Loading

0 commit comments

Comments
 (0)