nextSibling vs childNodes
JavaScript performance comparison
Preparation code
<div id="container">
<p>Child</p>
<p>Child</p>
<p>Child</p>
<p>Child</p>
<p>Child</p>
<p>Child</p>
<p>Child</p>
<p>Child</p>
<p>Child</p>
<p>Child</p>
</div>
<script>
var container = document.getElementById('container');
function process(element) {}
</script>
Preparation code output
<div id="container">
<p>Child</p>
<p>Child</p>
<p>Child</p>
<p>Child</p>
<p>Child</p>
<p>Child</p>
<p>Child</p>
<p>Child</p>
<p>Child</p>
<p>Child</p>
</div>
Test runner
Warning! For accurate results, please disable Firebug before running the tests. (Why?)
Java applet disabled.
Test | Ops/sec | |
---|---|---|
childNodes
|
|
pending… |
childNodes, cached
|
|
pending… |
nextSibling
|
|
pending… |
Compare results of other browsers
Revisions
You can edit these tests or add even more tests to this page by appending /edit
to the URL.
- Revision 1: published Adrian Sutton
- Revision 2: published
- Revision 3: published
- Revision 4: published TimTucker
- Revision 5: published Nick
- Revision 7: published
- Revision 8: published Sam3000
- Revision 9: published Sam3000
- Revision 10: published
- Revision 11: published
- Revision 12: published
- Revision 13: published
- Revision 15: published Yanis Benson
- Revision 16: published
- Revision 17: published askd
- Revision 20: published
- Revision 21: published Peter
- Revision 22: published
- Revision 23: published omg
- Revision 24: published rob1
- Revision 25: published
- Revision 26: published mixed
- Revision 28: published
- Revision 29: published
0 Comments