16

I often use the method getElementById("id1"); in my methods. I use it to find certain elements in my HTML. I wonder if I need to be concerned about how much I use it if it has to search the entire DOM every time.

How does this method work? Does it parse the DOM and return the element when it is found, or does it have all those values indexed somehow and so is able to return more quickly?

P.S. I am curious about the method in general, but I am using an Android WebView if that makes any difference.

Jon
  • 1,820
  • 2
  • 19
  • 43

3 Answers3

20

getElementById is very fast and you shouldn't have to worry about performance.

If you are using the same ID over and over (and over and over) again, you might want to cache it. The performance gain is neglectable:

var myId = getElementById("myId");
myId.operation1();
myId.operation2();
myId.andSome5000MoreCalls();

Check this SO answer for some benchmarks. The results Mike posted were:

IE8 getElementById: 0.4844 ms
IE8 id array lookup: 0.0062 ms

Chrome getElementById: 0.0039 ms
Chrome id array lookup: 0.0006 ms

Firefox 3.5 was comparable to chrome.

Community
  • 1
  • 1
Laoujin
  • 9,962
  • 7
  • 42
  • 69
  • 15
    neglectable (something you can neglect) != negligable (something so small as to be unmesurable) – Jamiec Sep 20 '12 at 14:46
  • Neglectable? Maybe for web application, but surely not if you develop a JS game! I think it's worth to mention – Lis Oct 02 '18 at 15:52
  • It would be more interesting to benchmarks performed on DOM trees having deep hierarchies and numerous nodes. – Lonnie Best Dec 01 '18 at 21:55
8

In fact getElementById is the fastest way to access an element in the DOM. Indexing depends on the specific browser, but here is a benchmark for it:

http://jsperf.com/getelementbyid-vs-everyone-else

Konstantin Dinev
  • 34,219
  • 14
  • 75
  • 100
4

Elements with IDs are indeed indexed, selecting an element by its ID through the DOM function is the most efficient way of selection.

Simon
  • 7,182
  • 2
  • 26
  • 42