Toggle navigation
MeasureThat.net
Create a benchmark
Tools
Feedback
FAQ
Register
Log In
JavaScript Array: Every-not vs not-Some
(version: 1)
Compare the performance of using the Every and Some method in an Array
Comparing performance of:
Using Every-not vs Using not-Some
Created:
2 months ago
by:
Guest
Jump to the latest result
Script Preparation code:
var statuses = [true, true, true, true, true, true, true, true, true, false, true, false, true, true, false]; statuses = statuses.map(s => !s);
Tests:
Using Every-not
const allFalse = statuses.every(status => !status); console.log(allFalse);
Using not-Some
const allFalse = !statuses.some(status => status); console.log(allFalse);
Rendered benchmark preparation results:
Suite status:
<idle, ready to run>
Run tests (2)
Previous results
Fork
Test case name
Result
Using Every-not
Using not-Some
Fastest:
N/A
Slowest:
N/A
Latest run results:
Run details:
(Test run date:
one month ago
)
User agent:
Mozilla/5.0 (Android 15; Mobile; rv:148.0) Gecko/148.0 Firefox/148.0
Browser/OS:
Firefox Mobile 148 on Android
View result in a separate tab
Embed
Embed Benchmark Result
<iframe src="https://measurethat.net/Embed?id=626492" width="100%" height="500px"></iframe>
Test name
Executions per second
Using Every-not
65788.6 Ops/sec
Using not-Some
66455.1 Ops/sec
Related benchmarks:
xxxxxxx
xxxxxxx
xxxxxxx
difference ! and === and ==
Object vs Boolean
!!a && b or a && b
JavaScript Array: Every vs Some
String comparison vs boolean check
Set#has() vs Array#includes()
Comments
Confirm delete:
Do you really want to delete benchmark?