Benchmark: Setting the same value with setAttribute()

Setting the same value with setAttribute() (version: 5)

Is checking the current value of an attribute with getAttribute() better than setting the same value with setAttribute() over and over.

Comparing performance of: set the same value vs check and set nothing vs check and set a new value vs set a new value vs check cache and set nothing vs check cache and set a new value

Created: one year ago by: Registered User

Jump to the latest result

HTML Preparation code:

<svg version="1.1"
     width="300" height="200"
     xmlns="http://www.w3.org/2000/svg">
  <rect id="rect1" width="100" height="100" fill="red" />
</svg>

Script Preparation code:

var rect = document.getElementById('rect1');
var width = Number(rect.getAttribute('width'));

Tests:

set the same value
rect.setAttribute('width', width);
check and set nothing
if (rect.getAttribute('width') !== `${width}`) { alert('this code does not run'); }
check and set a new value
if (rect.getAttribute('width') !== `${++width}`) { rect.setAttribute('width', width); }
set a new value
rect.setAttribute('width', ++width);
check cache and set nothing
const cache = width; if (cache !== width) { alert('this code does not run'); }
check cache and set a new value
const cache = width; if (cache !== ++width) { rect.setAttribute('width', width); }

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
set the same value
check and set nothing
check and set a new value
set a new value
check cache and set nothing
check cache and set a new value

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: one year ago)

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:101.0) Gecko/20100101 Firefox/101.0

Browser/OS: Firefox 101 on Mac OS X 10.15

View result in a separate tab

Test name	Executions per second
set the same value	16102210.0 Ops/sec
check and set nothing	12543280.0 Ops/sec
check and set a new value	2094075.0 Ops/sec
set a new value	2681240.0 Ops/sec
check cache and set nothing	1508090000.0 Ops/sec
check cache and set a new value	2535446.0 Ops/sec

Setting the same value with setAttribute() (version: 5)

Is checking the current value of an attribute with getAttribute() better than setting the same value with setAttribute() over and over.

Comparing performance of: set the same value vs check and set nothing vs check and set a new value vs set a new value vs check cache and set nothing vs check cache and set a new value

Created: one year ago by: Registered User

Jump to the latest result

set the same value

check and set nothing

check and set a new value

set a new value

check cache and set nothing

check cache and set a new value

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A