Benchmark: charCodeAt vs codePointAt actually using unicode chars

Script Preparation code:

var str = "some str😀ing heresome string he😀resome string heresome st😀ring heresome str😀ing heresome 😀string heresome string heres😀ome string heresome string heresome stri😀g heresome string heresome string heresome str😀ing heresome string heresome string heresome string her😀😀😀😀esome string heresome string here😀some string here"

Tests:

charCodeAt
str.charCodeAt(20)
codePointAt
str.codePointAt(20)

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
charCodeAt
codePointAt

Fastest: N/A

Slowest: N/A

ⓘ Get performance results from real users on your website with Request Metrics.

Website Performance Monitoring by Request Metrics

Latest run results:

Run details: (Test run date: 19 hours ago)

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:125.0) Gecko/20100101 Firefox/125.0

Browser/OS: Firefox 125 on Windows

View result in a separate tab

Test name	Executions per second
charCodeAt	1053981000.0 Ops/sec
codePointAt	1058923000.0 Ops/sec

charCodeAt vs codePointAt actually using unicode chars (version: 0)

Comparing performance of: charCodeAt vs codePointAt

Created: 2 years ago by: Guest

Jump to the latest result

charCodeAt

codePointAt

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A