Toggle navigation
MeasureThat
.net
Create a benchmark
Tools
Feedback
FAQ
Register
Log In
_.isEmpty vs Object.keys.length vs custom isEmpty method (10) alt is empty
(version: 1)
Comparing performance of:
_.isEmpty vs Object.keys().length vs isEmpty
Created:
one year ago
by:
Guest
Go to the latest result
HTML Preparation code:
<script src="https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.4/lodash.min.js"></script>
Script Preparation code:
window.obj = {}; function isEmpty(obj) { for (const prop in obj) return false return true; }
Tests:
_.isEmpty
_.isEmpty(window.obj);
Object.keys().length
Object.keys(window.obj).length === 0;
isEmpty
isEmpty(window.obj)
Rendered benchmark preparation results:
Suite status:
<idle, ready to run>
Run tests (3)
Previous results
Fork
Test case name
Result
_.isEmpty
Object.keys().length
isEmpty
Fastest:
N/A
Slowest:
N/A
Latest run results:
Run details:
(Test run date:
one year ago
)
User agent:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36
Browser/OS:
Chrome 131 on Mac OS X 10.15.7
View result in a separate tab
Embed
Embed Benchmark Result
<iframe src="https://measurethat.net/Embed?id=579145" width="100%" height="500px"></iframe>
isEmpty
143.3M/s
Object.keys().length
119.7M/s
_.isEmpty
27.7M/s
View exact numbers
Test name
Executions per second
✓
isEmpty
143,264,368 Ops/sec
Object.keys().length
119,679,872 Ops/sec
_.isEmpty
27,741,626 Ops/sec
Autogenerated LLM Summary
(model
gpt-4o-mini
, generated one year ago):
This benchmark evaluates three different methods for checking if an object is empty in JavaScript. The methods being compared are: 1. **Lodash's `_.isEmpty`** 2. **Using `Object.keys().length`** 3. **A custom function `isEmpty`** ### Methods Overview: 1. **Lodash's `_.isEmpty`**: - **Description**: This is a utility function provided by the Lodash library, a popular JavaScript utility library that provides functions for common programming tasks. `_.isEmpty` checks if an object, collection, map, or set is empty. - **Pros**: - Simple and straightforward to use. - Handles a variety of data types (objects, arrays, maps, etc.). - Well-optimized and tested with many edge cases in mind. - **Cons**: - Requires including the Lodash library, increasing bundle size if not already being used in the project. - May be slower compared to direct checks due to its additional features and overhead. 2. **Using `Object.keys().length`**: - **Description**: This method checks the number of keys in an object. If an object is empty, it will have no keys, and thus its length will be zero. - **Pros**: - Pure JavaScript solution, no external library required. - Generally faster and more lightweight compared to utility libraries. - **Cons**: - Only works with plain objects; doesn't handle other collections like arrays or maps directly. - Might not be as clear to read as using a dedicated function like `_.isEmpty`. 3. **Custom Function `isEmpty`**: - **Description**: This function uses a `for...in` loop to iterate over the properties of the object. If it finds any property, it returns false; otherwise, it returns true. - **Pros**: - Customizable and specific to the needs of the implementation. - No external dependencies, making it lightweight. - **Cons**: - Less performant than `Object.keys().length` for larger objects due to iteration. - May not handle certain edge cases (like prototype properties) without additional logic. ### Benchmark Results and Considerations: The benchmark results show the execution speed of each method, measured in "Executions Per Second": - **`isEmpty`**: 27,741,626 Executions/Second - **`Object.keys().length`**: 119,679,872 Executions/Second - **`_.isEmpty`**: 143,264,368 Executions/Second ### Summary of Results: The results indicate: - `_.isEmpty` is the fastest among the three, likely due to its optimizations in the Lodash library. - `Object.keys().length` is considerably faster than the custom `isEmpty` method, indicating that the simplicity of checking key lengths is efficient. - The custom `isEmpty` function is the slowest, primarily due to the overhead of iterating over properties. ### Alternatives and Other Considerations: - Other alternatives include using ES6 features like `Object.entries()` or `Object.values()`. Each serves the purpose of checking object emptiness but may have differing performance profiles and complexity. - Developers should consider trade-offs between performance and code readability/maintenance. If performance is a critical factor and the code is run frequently on large datasets, using `Object.keys().length` might be preferred. Conversely, if code clarity and maintainability are critical, `_.isEmpty` might be the better choice if Lodash is already part of the project. In conclusion, the ideal approach to determine if an object is empty depends on the context of the project, the frequency of calls, and whether external libraries are in use. Each method serves its purpose effectively in different scenarios.
Related benchmarks
_.isEmpty vs Object.keys.length
_.isEmpty vs You-Dont-Need-Lodash-Underscore#_isempty
_.isEmpty() vs Object.keys().length empty objects
Object no keys vs isEmpty
_.isEmpty vs Object.keys.length (10)
_.isEmpty vs Object.keys.length vs custom isEmpty method (10000) alt is empty
Comments
Confirm delete:
Do you really want to delete benchmark?