Custom pluck test vs JS map vs lodash map (version: 3)

Testing a functional programming method 'pluck'. This is an in-progress test. Taken from lodash source code, using the Array constructor to make an Array of a specified length, seems to have a considerable impact on performance. In my simple pluck implementation, not using the constructor e.g. const plucked = [], was considerably slower.

Comparing performance of: my pluck function with skipNone vs native JS map and filter vs lodash _.map and iteratee vs my pluck function without skipNone vs native JS map vs lodash _.map

Created: one year ago by: Registered User
Go to the latest result
HTML Preparation code:
Script Preparation code:
Tests:
Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results
  • Test case name Result
    my pluck function with skipNone
    native JS map and filter
    lodash _.map and iteratee
    my pluck function without skipNone
    native JS map
    lodash _.map

    Fastest: N/A

    Slowest: N/A

Latest run results:
Run details: (Test run date: one year ago)
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36
Chrome 130 on Windows
View result in a separate tab
my pluck function without skipNone
336K/s
lodash _.map
192K/s
native JS map
173K/s
my pluck function with skipNone
159K/s
lodash _.map and iteratee
3K/s
native JS map and filter
3K/s
View exact numbers
Test name Executions per second
✓ my pluck function without skipNone 336,110 Ops/sec
lodash _.map 192,012 Ops/sec
native JS map 172,821 Ops/sec
my pluck function with skipNone 159,371 Ops/sec
lodash _.map and iteratee 3,206 Ops/sec
native JS map and filter 2,784 Ops/sec

Related benchmarks