Toggle navigation
MeasureThat
.net
Create a benchmark
Tools
Feedback
Feature Requests
FAQ
Register
Log In
charAt vs codePointAt actually using unicode chars
(version: 1)
Benchmark.js
Comparing performance of:
charAt vs codePointAt
Created:
6 months ago
by:
Registered User
Go to the latest result
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:
charAt
str.charAt(20)
codePointAt
str.codePointAt(20)
Rendered benchmark preparation results:
Suite status:
<idle, ready to run>
Run tests (2)
Previous results
Fork
Test case name
Result
charAt
codePointAt
Fastest:
N/A
Slowest:
N/A
Latest run results:
Run details:
(Test run date:
6 months ago
)
User agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36
Browser/OS:
Chrome 145 on Windows
View result in a separate tab
Embed
Embed Benchmark Result
<iframe src="https://measurethat.net/Embed?id=625993" width="100%" height="500px"></iframe>
charAt
268.0M/s
codePointAt
255.3M/s
View exact numbers
Test name
Executions per second
✓
charAt
267,951,072 Ops/sec
codePointAt
255,252,304 Ops/sec
Related benchmarks
charCodeAt vs []
charCodeAt vs codePointAt
charCodeAt vs codePointAt actually using unicode chars
string.charCodeAt(index) vs string[index].charCodeAt()
string.charCodeAt(index) vs string[index].charCodeAt() vs +string[index]
charCodeAt vs [] comparison
Comments
Confirm delete:
Do you really want to delete benchmark?