Can deepStrictEqual inside pushDevSchema.ts be swapped for dequal?

[jeepman32]

Hi there! Loving Payload CMS so far, but I've hit a big snag.

The assert.deepStrictEqual based schema-change detector consumes huge amounts of memory and takes a huge amount of time to complete when facing moderately complex schemas. In my case it consumed 21GB of memory and took 2 minutes 48 seconds to complete.

Here is a link to the schema in question. It is fed into the right-hand side of deepStrictEquals: My schema.

Below is a screenshot of the near-peak memory usage, and a screenshot of the times. The respective method is included before each time to completion.

Memory Usage	Time to completion

I did some hacky testing and swapped in dequal which completed the check in 1.673s. I also tried out fast-deep-equals but I found dequal to be more suitable for the task, and a more suitable replacement.

Would a swap from assert.deepStrictEqual to dequal or a similar pacakge be an appropriate feature, and a feature that is desired? It appears to be low-hanging fruit that would make Postgres, and possibly SQLite much faster for devs using them!

Thanks!

[jeepman32]

Draft PR has been created, just in case anyone wanted to see the impacts or test the improvements! I'm currently dogfooding the change, replacing the official @payloadcms/drizzle with the one in my branch. Initial impressions are very good.

[jeepman32]

Resolved by dequal replacing assert.deepEqual!