Benchmark: [compareDocumentPosition vs contains] performance 2

HTML Preparation code:

<html>
  <head>
  </head>
  <body>
    <div id="div">
    	<div id="a">
   		</div>
    </div>
    <div id="b">
    </div>
  </body>
</html>

Tests:

compareDocumentPosition
const { div, a, b } = window for (let i = 0; i < 100; i++) { const compare = div.compareDocumentPosition(a) compare & 16 const compare2 = div.compareDocumentPosition(b) compare2 & 16 }
contains
const { div, a, b } = window for (let i = 0; i < 100; i++) { div.contains(a) div.contains(b) }

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
compareDocumentPosition
contains

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: 5 months ago)

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0

Browser/OS: Chrome 145 on Windows

View result in a separate tab

contains

215K/s

compareDocumentPosition

95K/s

View exact numbers

Test name	Executions per second
✓ contains	214,653 Ops/sec
compareDocumentPosition	95,312 Ops/sec

[compareDocumentPosition vs contains] performance 2 (version: 1)

Comparing performance of: `compareDocumentPosition vs contains`

Created: 5 months ago by: Guest

Go to the latest result

compareDocumentPosition

contains

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

[compareDocumentPosition vs contains] performance 2 (version: 1)

Comparing performance of: compareDocumentPosition vs contains

Created: 5 months ago by: Guest

Go to the latest result

compareDocumentPosition

contains

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Related benchmarks

Comparing performance of: `compareDocumentPosition vs contains`