Markus Junginger
Markus Junginger
Most queries should perform in a few milliseconds (or sub-milliseconds) - if they have a proper index. Maybe you can pinpoint the slowdown, e.g. by performance logging (measure the duration...
> The issue itself seems to be with getAllAsync() @Mairramer How many objects do you have?
please double check that - it would be extremely surprising for a `store.box().getAllAsync()` without any object to take more than a few milliseconds. There's no way this takes 6 seconds...
If there really are no objects, relations will not matter. It'd be helpful if you could actually pinpoint the issue. How do you know it is related to ObjectBox? We'd...
> I could switch to using store.box().getAll() instead I just wanted to suggest the same... 🙂 Performance wise this should be fine for a couple thousand objects (milliseconds).
I'm seriously impressed how bad isolates are. 🤯
Thanks for the input, all good and well. Regarding implementation details, I doubt we'll go with a long lived isolate. We already have async write ops on the native side....
I guess these must be immutable. By using `static let` instead of `static var`, you’re making the properties immutable and inherently thread-safe, which satisfies Swift’s concurrency rules.
Btw, why are you requesting React Native, and not JavaScript support in general?
No immediate plans yet. Are there any ready-to-use cross-compilers, e.g. like ARM offers them? Can you tell a bit about use cases? And why are you bound to this CPU?