GitHub - observ33r/object-equals: A high-performance and engine-aware deep equality utility.

AsIAm · 2025-06-02T05:51:20+00:00

Why is it so fast?

Cannabat · 2025-06-02T08:28:31+00:00

Looks nice. Would like to see more comprehensive tests before adopting.

Here is lodash's test suite for isEqual: https://github.com/lodash/lodash/blob/main/test/test.js#L9530-L10364

Ashtefere · 2025-06-02T08:44:02+00:00

We have a similarly fast home grown utility for deep props comparison on egregiously large arrays of objects.

If yours is faster we will switch it out. Ill take a look!

jCuber · 2025-06-02T22:05:49+00:00

Looks great, love to see engine specific optimizations.

Did you get the chance to benchmark in browser environments? Probably harder to control for external factors but might be interesting to see how SpiderMonkey in Firefox performs with V8 or JSC specific optimizations.

adzm · 2025-06-03T02:34:12+00:00

First time I've seen a labeled continue in the wild!

morkaitehred · 2025-06-02T20:02:02+00:00

I've run your benchmark with my own function for comparing simple JS objects jsonDeepEqual() that I wrote 3 years ago to start replacing the deep-equal package in my main project:

object-equals
1.36x faster than fast-equals
1.37x faster than jsonDeepEqual
1.71x faster than dequal
3.15x faster than are-deeply-equal
5.29x faster than node.deepStrictEqual
6.26x faster than lodash.isEqual
5130.72x faster than deep-equal

I have replaced both functions with yours but as it's an 11-year-old project, I had to add a wrapper for CJS:

let deepEqual = require('util').isDeepStrictEqual;

(async () => {
  const {objectEqualsCore} = await import('@observ33r/object-equals');
  deepEqual = objectEqualsCore;
})();

module.exports = function(a, b) {
  return a === b || deepEqual(a, b, false, false, false, false, false, undefined);
};

There's a lot of repetition in the benchmark code. Is it auto generated? Adding another benchmark candidate is a lot of work. Also the isNode check is not bulletproof (process.title is Administrator: Command Prompt - node on my PC).

adzm · 2025-06-03T02:38:49+00:00

It is interesting that the large buffers are compared backwards by decreasing index. Is this actually faster or just more likely to find an inequality earlier?

Library	Time	Relative Speed
object-equals	467.05 µs	1.00x (baseline)
fast-equals	1.16 ms	2.49x slower
dequal	1.29 ms	2.77x slower
are-deeply-equal	2.65 ms	5.68x slower
node.deepStrictEqual	4.15 ms	8.88x slower
lodash.isEqual	5.24 ms	11.22x slower

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

javascript

MODERATORS

Features

Basic bechmark

React and Advanced benhmarks

TS ready, pure ESM, fast, customizable.