Run results for: Traverse function vs NodeIterator vs TreeWalker

Run details:

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

Browser: Chrome 106

Operating system: Windows

Device Platform: Desktop

Date tested: 2 years ago

TreeWalker with filter param

362K/s

NodeIterator with filter param

343K/s

Traverse function

48K/s

TreeWalker with filter function

17K/s

NodeIterator with filter function

6K/s

View exact numbers

Test name	Executions per second
✓ TreeWalker with filter param	361,578 Ops/sec
NodeIterator with filter param	342,809 Ops/sec
Traverse function	48,414 Ops/sec
TreeWalker with filter function	17,360 Ops/sec
NodeIterator with filter function	6,339 Ops/sec

Script Preparation code:

// language=HTML
const html = `
    <!-- article out start -->
    <article>
        <!-- article in start -->
        <h1>Lorem ipsum</h1>
        <p>Lorem ipsum dolor sit amet, consectetur adipisicing elit. Cumque, nostrum.</p>
        <!-- article in end -->
    </article>
    <!-- article out end -->

    <!-- article out start -->
    <article>
        <!-- article in start -->
        <h1>Lorem ipsum</h1>
        <p>Lorem ipsum dolor sit amet, consectetur adipisicing elit. Cumque, nostrum.</p>
        <!-- article in end -->
    </article>
    <!-- article out end -->

    <!-- article out start -->
    <article>
        <!-- article in start -->
        <h1>Lorem ipsum</h1>
        <p>Lorem ipsum dolor sit amet, consectetur adipisicing elit. Cumque, nostrum.</p>
        <!-- article in end -->
    </article>
    <!-- article out end -->
`;
const template = document.createElement('template');
template.innerHTML = html;

window.testTemplate = template;

window.testTraverse = function traverse(node, use) {
    if (!node) return;

    use(node);
    traverse(node.firstChild, use);
    traverse(node.nextSibling, use);
}

Tests: