Run results for: Cached vs new Intl.DateTimeFormat

Run details:

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36

Browser: Chrome 114

Operating system: Mac OS X 10.15.7

Device Platform: Desktop

Date tested: 10 months ago

Test name	Executions per second
new Intl.DateTimeFormat.format(date)	9200.6 Ops/sec
cached Intl.DateTimeFormat.format(date)	360932.4 Ops/sec
new Intl.DateTimeFormat.format(number)	9271.0 Ops/sec
cached Intl.DateTimeFormat.format(number)	388306.3 Ops/sec

Script Preparation code:

const TWO_DIGIT = '2-digit';

var options = {
      month: TWO_DIGIT,
      year: 'numeric',
      day: TWO_DIGIT,
      hour: TWO_DIGIT,
      hour12: false,
      minute: TWO_DIGIT,
      second: TWO_DIGIT,
    }

var cached = new Intl.DateTimeFormat('en-US', options);
var date = new Date();
var number = date.getTime();

Tests:

new Intl.DateTimeFormat.format(date)
new Intl.DateTimeFormat('en-US', options).format(date);
cached Intl.DateTimeFormat.format(date)
cached.format(date);
new Intl.DateTimeFormat.format(number)
new Intl.DateTimeFormat('en-US', options).format(number);
cached Intl.DateTimeFormat.format(number)
cached.format(number);

Run results for: Cached vs new Intl.DateTimeFormat

measure the perf impact of caching calls to new Intl.DateTimeFormat

new Intl.DateTimeFormat.format(date)

cached Intl.DateTimeFormat.format(date)

new Intl.DateTimeFormat.format(number)

cached Intl.DateTimeFormat.format(number)