Re: [WICG/webcomponents] Jan 2024 DOM Parts Quarterly Meeting (Issue #1027)

>
> It includes a bit of a description of the methodology on the page itself. Certainly it has a lot of built-in assumptions, but most are semi-defensible. I'm very interested to hear if you have any feedback about the methodology!

One feedback we can immediately give is that using the same n across browsers would be better so that there won't be differences in things like compilation time, GC pauses, etc... Using n=200,000, the difference between Safari & Chrome seems somewhat smaller. I'd remember to share any additional feedback we find as we analyze this test :)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/1027#issuecomment-1911088335
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/1027/1911088335@github.com>

Received on Thursday, 25 January 2024 22:17:14 UTC