Ladislav Jochman

@zlove Thx a lot for your fix, I owe you a beer. Works like a charm!

Seriously, you need to put this in the official plugin :+1:

Note: I will add one more performance report tommorow. We have a selector querying 20000 objects and then filtering them. Currently it takes ~500ms for DB query and another ~500ms...

Access to the source code won't be possible unfortunately, as this is a client's project behind NDA. I can share some extra snippets if needed (our Dexie -> Redux selectors...

@dfahlander I've run another set of tests with much bigger table. I've also tried to upgrade to Dexie 3.0.3, with no measurable effect on performance. If you're interested, I can...

@dfahlander I've tried to put our whole selector stack (from DB to React) in this example. Business logic was removed as it's not important for tests. All performance results were...

I believe we only create one instance per page mount (as we define it once and then use that instance to access any database selector). Is there an easy way...

It's possible that our abstraction layer is creating some sort of bottleneck. I'll test the number of connections and report back. Whole implementation is outlined in the "example" stack comment....