Benchmark: update vs rerender

HTML Preparation code:

<ul id="update-list">
      <li>A</li>
      <li>B</li>
      <li>C</li>
      <li>D</li>
      <li>E</li>
    </ul>

    <ul id="rerender-list">
      <li>A</li>
      <li>B</li>
      <li>C</li>
      <li>D</li>
      <li>E</li>
    </ul>

Tests:

update
[].slice .call(document.querySelectorAll("#update-list li")) .forEach( (li, idx) => { li.textContent += " " + idx; });
rerender
const fragment = document.createDocumentFragment(); [].slice .call(document.querySelectorAll("#rerender-list li")) .forEach((li, idx) => { const newLi = document.createElement("li"); newLi.textContent = li.textContent + " " + idx; fragment.appendChild( newLi ); }); const list = document.querySelector("#rerender-list"); list.innerHTML = ""; list.appendChild(fragment);

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
update
rerender

Fastest: N/A

Slowest: N/A

ⓘ Get performance results from real users on your website with Request Metrics.

Website Performance Monitoring by Request Metrics

Latest run results:

Run details: (Test run date: 7 years ago)

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36

Browser/OS: Chrome 53 on Mac OS X 10.11.3

View result in a separate tab

Test name	Executions per second
update	3948.7 Ops/sec
rerender	4366.0 Ops/sec

update vs rerender (version: 0)

Comparing performance of: update vs rerender

Created: 7 years ago by: Guest

Jump to the latest result

update

rerender

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A