Tom Duncalf

By way of an update @liamjones, I've found that the way we are accessing the native Realm C++ objects in [v11 via JSI](https://github.com/realm/realm-js/blob/v11/src/jsi/jsi_class.hpp#L493) performs quite a lot slower than the...

@HSReact I don't have any benchmarks on those. The only place we would expect to see any change in performance characteristics is in the JS/C++ interop layer (previously JSC, now...

I'll document the workaround for when Hermes is enabled here in case you want to try it, but it's pretty ugly! There are probably ways to neaten it up (e.g....

Ah OK, we don't have a workaround for that case yet. I'll update this issue when we have a fix though

Hey @tradebulls, thanks for letting me know – I'll take a look at the new release and see. They mention they are now building Hermes from source so hopefully this...

It looks like this will require some work from our side to support, if I drop the new React Native into our Hermes branch I get a Hermes error. We...

Hey @tradebulls, unfortunately I'm still seeing a performance regression with the latest RN. I'm following up with Meta to see what we can do mitigate this.

I've confirmed that this change did not make it to RN 0.69, but should be in RN 0.70 which should hopefully be out fairly soon.

Obviously I can't make any commitments for the Meta team, but it sounded like they were hoping to get this out sooner than that

@tradebulls I think that's something different. The issue causing the regression is [this timer code in Hermes](https://github.com/facebook/hermes/blob/main/API/hermes/hermes.cpp#L188-L194) which times every C++ JS call, which results in a lot of extra...