Stefan Krause

Thanks. Read about it on hacker news and reddit and was looking forward getting a PR ;-) But it seems like we have to work a few things out. There...

That would be really interesting. But I'd rather put it into a seperate repo. Some questions would have to be answered: * What form/layout are we measuring? I'd say lots...

Here's the first result: https://krausest.github.io/js-framework-benchmark/2022/table_chrome_103_mem10k.html The spread is really big - pretty interesting. What do you think? Is there a memory benchmark that we could drop instead?

Thanks - here's some information about how I calculate the memory values: The benchmark performs a GC (`HeapProfiler.collectGarbage`) and then calls `Performance.getMetrics` which reports among other values: { name: 'JSHeapUsedSize',...

Back to @fabiospampinato and the problem with the "reliable measure". I'm really close to giving up on measuring memory. Here are values that I could use (I'm putting a long...

Thanks. A heap snapshot is performed before all the measurements above. (https://github.com/krausest/js-framework-benchmark/blob/master/webdriver-ts/src/forkedBenchmarkRunnerPuppeteer.ts#L59 a bit verbose for puppeteer or https://github.com/krausest/js-framework-benchmark/blob/master/webdriver-ts/src/forkedBenchmarkRunnerPlaywright.ts#L207 for playwright) @paulirish It would be great if you shed a...

So - another run has finished (the duration for the whole run is about 15 hours - almost too long): https://krausest.github.io/js-framework-benchmark/2022/table_chrome_103_mem10k_2.html The following is now implemented: - Memory is now...

Almost great - performance.measureUserAgentSpecificMemory() doesn't work headless neither for playwright nor for puppeteer: https://github.com/puppeteer/puppeteer/issues/8258

@paulirish Great - seems like it even works on OSX! I could remove the special handling again! Thanks a lot.

@michaelboulton Do you have an idea how to get the build working again?