Run results for: json stringify vs object tostring number thresholds

Run details:

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

Browser: Chrome 128

Operating system: Mac OS X 10.15.7

Device Platform: Desktop

Date tested: one year ago

toString number

26.0M/s

toString undefined

10.1M/s

JSON.stringify number

8.4M/s

JSON.stringify undefined

5.6M/s

JSON.stringify array

5.2M/s

toString array

5.1M/s

View exact numbers

Test name	Executions per second
✓ toString number	26,034,676 Ops/sec
toString undefined	10,100,495 Ops/sec
JSON.stringify number	8,386,008 Ops/sec
JSON.stringify undefined	5,602,038 Ops/sec
JSON.stringify array	5,196,670 Ops/sec
toString array	5,074,846 Ops/sec

Script Preparation code:

function makeTestDataNum() { return 0; }

function makeTestDataUndef() { return undefined; }

function makeTestDataArray() { return [0, 0.4, 0.6, 1]; }

Tests:

toString number
const d = makeTestDataNum() d ? d.toString() : "0"
JSON.stringify number
JSON.stringify(makeTestDataNum());
toString undefined
const d = makeTestDataUndef() d ? d.toString() : "0"
JSON.stringify undefined
JSON.stringify(makeTestDataUndef());
toString array
const d = makeTestDataArray() d ? d.toString() : "0"
JSON.stringify array
JSON.stringify(makeTestDataArray());