Kelly Milligan

totally get it. so far I have a decent sandbox, but am unable to reproduce. the app i'm working on is incredibly complex(I know we all say that), so it...

my guess is that is a huge number of small things adding up.

every `memoize` in that stack for 4.1.5 is coming from this block in reselect in defaultMemoize:  every anonymous there in the long stack of back and forth between anonymous...

with just regular reselect selector, same result for 4.1.5 and re-reselect: ```ts export const getCalendarSquareCalendar = createSelector( calendarSquaresByTableAndTimeSelector, calendarSquareId, dateTimeString, tableId, getCalendarSquareById ); ``` and 

looks the same with a max size option as well: ```ts export const getCalendarSquareCalendar = createSelector( calendarSquaresByTableAndTimeSelector, calendarSquareId, dateTimeString, tableId, getCalendarSquareById, { memoizeOptions: { maxSize: 1000, }, } ); ```

also tried above with the result option, using shallowEqual. same result. tried a pattern for creating a new selector instance for each component instead, similar results.

yeah, working on it. just wanted to try out the suggestions above, and report back. here's 4.0.0 with creating a new selector instance for each component: 

and runs just night and day faster.

same question :)

VirtioFS is helping some for me locally, but still pretty slow if you're iterating on a Dockerfile for development purposes.