Run results for: Testing JS Performance of deleting a large map.

In FF if the object being iterated over is large enough it will trigger an expensive cycle collection with Test #1. Test #2 runs approximately 100 times faster on FF. The difference is marginal in Chrome. To see the difference in timing, I recommend loading up the debugger console to see exactly how many ms each run takes.

Run details:

User agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36 OPR/40.0.2308.90

Browser: Opera 40

Operating system: Windows

Device Platform: Other

Date tested: 8 years ago

Test name	Executions per second
Using hasOwnProperty	6.9 Ops/sec
Using Object.keys()	8.5 Ops/sec
Skipping hasOwnProperty()	7.2 Ops/sec

Script Preparation code:

var map = {};

function generateSequence(prefix, numItems) { 
  var buffer = [];
  var prefixInstance = prefix || "";
  for (var i = 0; i < numItems; i++) {
    buffer.push(prefix + i);
  }
  return buffer;
}

var startTime;
function startTimer() {
  startTime = new Date().getTime()
}
function stopTimer() {
  var endTime = new Date().getTime();
  console.log("Took " + (endTime - startTime) +  " ms");
}

function generateMap() {
  console.log("Generating");
  for (var i = 0; i < 50000; i++) {
	map["a-" + i] = { 
      a: generateSequence("aaaaaaaaa", 10)
    }
  }

}

Tests:

The slow version
generateMap(); console.log("Test #1"); startTimer(); for (key in map) { if (map.hasOwnProperty(key)) { delete map[key]; } } stopTimer();
Faster version using Object.keys().
generateMap(); console.log("Test #2"); startTimer(); var keys = Object.keys(map); for (var i = 0, ii = keys.length; i < ii; i++) { delete map[keys[i]]; } stopTimer();

Run results for: Testing JS Performance of deleting a large map.

The slow version

Faster version using Object.keys().