Greg D

Thanks for the quick response. I was just using Next by itself. Maybe "no preview mode" is something to add to the caveats on https://github.com/jthegedus/firebase-gcp-examples/tree/master/functions-nextjs#caveats .

I continued investigating and I isolated the cause to the custom `distDir` which we copied from the repo here. I don't know why that would be. Firebase does not seem...

> It would be odd to me that preview mode would require the default distDir so I think it's something else to do with Firebase. I agree but the same...

Yes that’s correct. Sent from my thumbs > On Sep 3, 2020, at 23:37, James Hegedus wrote: > >  > Oh, so you found an issue with preview mode...

Genetify uses a f-test to determine differences between n groups on a continuous variable. See http://en.wikipedia.org/wiki/F_statistic . The blog article describes a binomial test. The f-test is more general but...

Makes sense. You could enforce uniqueness in the goal.record method or in the DB. It depends on your definition of "unique".

I've had the same issue with some tests. Try modifying the weight function to make it optimize slower. Look at genetify.weight. https://github.com/gregdingle/genetify/blob/master/genetify/genetify.js#L1233

Could you try genetify.vary('elements') or another specific call as a workaround? See https://github.com/gregdingle/genetify/wiki/Usage

@hrsh7th @mweststrate this looks like a great PR to give users (like me) meaningfully better performance with large objects (>1000 keys). Was it closed just for lack of activity?

I patched my installation of immer with the key lines from #941 and **I got a decrease from 70ms to 3ms in my redux reducer** in a typical workload. #941...