I've been reading, and they're saying that associative arrays won't give you the same efficiency as arrays. An associative array can look things up in O(N) time, where an array can look things up in O(1).

Here's my question: which one would be more efficient in terms of looking up values quickly and not hogging too much memory?

Associative:

var myVars=new Array(); 
myVars['test1'] = a;
myVars['test2'] = b;
myVars['test3'] = c;
... (up to 200+ values)

echo myVars['test2'];

Stored Associative:

var myVars=new Array(); 
var TEST1 = 1;
var TEST2 = 2;
var TEST3 = 3;
... (up to 200+ values)

myVars[TEST1] = a;
myVars[TEST2] = b;
myVars[TEST3] = c;
... (up to 200+ values)

echo myVars[TEST2];

I've been reading, and they're saying that associative arrays won't give you the same efficiency as arrays. An associative array can look things up in O(N) time, where an array can look things up in O(1).

Here's my question: which one would be more efficient in terms of looking up values quickly and not hogging too much memory?

Associative:

var myVars=new Array(); 
myVars['test1'] = a;
myVars['test2'] = b;
myVars['test3'] = c;
... (up to 200+ values)

echo myVars['test2'];

Stored Associative:

var myVars=new Array(); 
var TEST1 = 1;
var TEST2 = 2;
var TEST3 = 3;
... (up to 200+ values)

myVars[TEST1] = a;
myVars[TEST2] = b;
myVars[TEST3] = c;
... (up to 200+ values)

echo myVars[TEST2];

• javascript
• arrays
• performance

• 4 FWIW there's no such thing as an associative array in Javascript... just an object with a similar access process. – Rudu Commented May 4, 2011 at 19:18
• 1 Test the performance yourself: jsperf.com/javascript-associative-vs-non-associative-arrays – Levi Morrison Commented May 4, 2011 at 19:38
• 1 Or this one: jsperf.com/object-vs-array-perf – Felix Kling Commented May 4, 2011 at 19:50
• 1 @Felix Your test is not realistic to his specific question. See my test. It disproves yours. Also, your object and array access testing is not well-thought out. You aren't comparing apples to apples. – Levi Morrison Commented May 4, 2011 at 19:54
• and another test jsben.ch/#/Y9jDP – EscapeNetscape Commented Oct 21, 2016 at 21:28

4 Answers 4

First, the first usage of Array is wrong. Although it is possible to do it, it does not mean you should. You are "abusing" the fact that arrays are objects too. This can lead to unexpected behaviour, e.g. although you add 200 values, myVars.length will be 0.

Don't use a JavaScript array as associative array. Use plain objects for that:

var myVars = {}; 
myVars['test1'] = a;
myVars['test2'] = b;
myVars['test3'] = c;

Second, in JavaScript there is no real difference between the two (objects and arrays). Arrays extend objects and add some behaviour, but they are still objects. The elements are stored as properties of the array.

You can find more information in the specification:

Array objects give special treatment to a certain class of property names. A property name P (in the form of a String value) is an array index if and only if ToString(ToUint32(P)) is equal to P and ToUint32(P) is not equal to 2³²−1. (...)

So both:

var obj = {'answer': 42};
obj['answer'];

and

var arr = [42];
arr[0];

have the same access time^†, which is definitely not O(n).

†: It is better to say should have. Apparently this varies in different implementations.

Apart from that, your second example is horrible to maintain. If you assign numbers to variables, why not use the numbers directly?

var myVars = []; 
myVars[0] = a;
myVars[1] = b;
myVars[2] = c;

Update:

More importantly: You have to choose the right data structure for your needs and this is not only determined by the access time of a single element, but also:

• Are the keys consecutive numbers or arbitrary strings/numbers?
• Do you have to access all (i.e. loop over all) elements of the collection?

Numerical arrays (arrays) and associative arrays (or hash tables/maps (objects in JS)) provide different solutions for different problems.

I posit that the present responses do not fully consider more practical use cases. I created this jsperf to demonstrate. While @Felix's jsperf demonstrates lookup speed, it's not performed on sufficiently large objects to be really useful. I think 10,000 simple properties is more reasonable. Further, you need to randomly select keys in the sequence to read, modify, delete and create to truly demonstrate the performance differences between the two types.

First of all, whoever they are, feel free to ignore them.

Every decent implementation of every decent scripting language, including JavaScript, will give you associative arrays that are either O(log(n)) access time, or else O(1) average access time, O(n) worst case (which you almost never hit). Either way in practice a lookup is fast.

Arrays have O(1) guaranteed access time, which is incredibly fast. But in some scripting languages (eg PHP) there isn't even a native array type provided. They just use associative arrays for both.

Answer: test it out yourself.

Update: After some back-and-forth with Felix, it appears that array access is usually faster than both associative arrays and objects. This is not always the case, notably in Chrome. In Chrome 11 on Ubuntu 11, arrays are faster. In Chrome 11 on Mac OS 10.6 there is no notable difference between them.

These tests did not measure manipulation, only reading.