Run results for: Traverse function vs NodeIterator vs TreeWalker

Run details:

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:132.0) Gecko/20100101 Firefox/132.0

Browser: Firefox 132

Operating system: Linux

Device Platform: Desktop

Date tested: one year ago

NodeIterator with filter param

2.5M/s

TreeWalker with filter param

1.9M/s

Traverse function

1.3M/s

TreeWalker with filter function

473K/s

NodeIterator with filter function

213K/s

View exact numbers

Test name	Executions per second
✓ NodeIterator with filter param	2,468,216 Ops/sec
TreeWalker with filter param	1,907,504 Ops/sec
Traverse function	1,348,292 Ops/sec
TreeWalker with filter function	472,741 Ops/sec
NodeIterator with filter function	212,990 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: