Toggle navigation
MeasureThat.net
Create a benchmark
Tools
Feedback
FAQ
Register
Log In
[compareDocumentPosition vs querySelector] performance
(version: 1)
Comparing performance of:
compareDocumentPosition vs contains
Created:
one year ago
by:
Guest
Jump to the latest result
HTML Preparation code:
<html> <head> </head> <body> <div id="div" data-attr> <div id="a" data-attr> </div> </div> <div id="b" data-attr> </div> </body> </html>
Tests:
compareDocumentPosition
const { div, a, b } = window for (let i = 0; i < 100; i++) { let compare = div.compareDocumentPosition(a) compare & 8 compare & 16 compare = div.compareDocumentPosition(b) compare & 8 compare & 16 }
contains
const { div, a, b } = window for (let i = 0; i < 100; i++) { const order = document.querySelectorAll('[data-attr]') }
Rendered benchmark preparation results:
Suite status:
<idle, ready to run>
Run tests (2)
Previous results
Fork
Test case name
Result
compareDocumentPosition
contains
Fastest:
N/A
Slowest:
N/A
Latest run results:
Run details:
(Test run date:
8 months ago
)
User agent:
Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Mobile Safari/537.36
Browser/OS:
Chrome Mobile 139 on Android
View result in a separate tab
Embed
Embed Benchmark Result
Test name
Executions per second
compareDocumentPosition
65220.1 Ops/sec
contains
14073.6 Ops/sec
Related benchmarks:
querySelectorAll vs getElementsByTagName [for loop]
Compare foreach
querySelectorAll vs getElementsByTagName iteration 2
querySelectorAll vs getElementsByTagName iteration with for
Compare contains vs closest v2
[compareDocumentPosition vs contains] performance
querySelectorAll vs getElementsByTagName iteration 22
querySelectorAll vs getElementsByTagName iteration 222
querySelectorAll vs getElementsByTagName iteration v2
Comments
Confirm delete:
Do you really want to delete benchmark?