Toggle navigation
MeasureThat.net
Create a benchmark
Tools
Feedback
FAQ
Register
Log In
Run results for:
new Intl.DateTimeFormat vs cached Intl.DateTimeFormat
measure the perf impact of caching calls to new Intl.DateTimeFormat
Go to the benchmark
Embed
Embed Benchmark Result
Run details:
User agent:
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.6613.648 YaBrowser/24.10.4.648 (beta) Yowser/2.5 Safari/537.36
Browser:
Yandex Browser 24
Operating system:
Linux
Device Platform:
Desktop
Date tested:
one year ago
Test name
Executions per second
new Intl.DateTimeFormat.format()
13492.0 Ops/sec
cached Intl.DateTimeFormat.format()
485826.3 Ops/sec
new Intl.DateTimeFormat.formatToParts
13488.5 Ops/sec
cached Intl.DateTimeFormat.formatToParts()
228143.7 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);
Tests:
new Intl.DateTimeFormat.format()
new Intl.DateTimeFormat('en-US', options).format(new Date());
cached Intl.DateTimeFormat.format()
cached.format(new Date());
new Intl.DateTimeFormat.formatToParts
new Intl.DateTimeFormat('en-US', options).formatToParts(new Date());
cached Intl.DateTimeFormat.formatToParts()
cached.formatToParts(new Date());