3 ms·
it wouldn't surprise me if the major bottlenecks in many applications are in the DOM access No question about it. I'm wondering why we're not seeing much work
by gruseom 18y ago
it wouldn't surprise me if the major bottlenecks in many applications are in the DOM access
No question about it. I'm wondering why we're not seeing much work being done in this area. Perhaps it's because the problems are messier and not as well defined (let alone as well researched) as things like method dispatch?
- othermaciej 18y agoWell if you put any stock in microbenchmarks, try this DOM in your favorite browsers: http://www.hixie.ch/tests/adhoc/perf/dom/artificial/core/001.html http://www.hixie.ch/tests/adhoc/perf/dom/artificial/core/001... Safari + ToT WebKit is way faster than the others.
- MaysonL 18y agoMacbook OS X 10.5.4 results FireFox 3.0 Total elapsed time: 1399ms Breakdown (fraction shows time relative to append time): Append: 1.00; 301ms Prepend: 1.49; 447ms Index: 0.32; 97ms Insert: 1.36; 410ms Remove: 0.48; 144ms Crossover Chromium Total elapsed time: 412ms Breakdown (fraction shows time relative to append time): Append: 1.00; 128ms Prepend: 0.90; 115ms Index: 0.28; 36ms Insert: 0.90; 115ms Remove: 0.14; 18ms Webkit Nightly Total elapsed time: 116ms Breakdown (fraction shows time relative to append time): Append: 1.00; 56ms Prepend: 0.29; 16ms Index: 0.36; 20ms Insert: 0.32; 18ms Remove: 0.11; 6ms