You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 14, 2023. It is now read-only.
Hello, thanks for this handy package! In Readme you're saying that using background compute can be slower. Could you please share sample data / describe in brief your findings?
I assume results heavily depend on particular device and parallelism implementation by different vendors.
But may be you can share some rough data just to know what to expect, like worse case scenarios, severity and share of problem cases you observed.
Thank you!
The text was updated successfully, but these errors were encountered:
I did use this implementation (got the project from someone else) and we do at startup 9 rest calls and every of them created an isolate with compute. I measured the app start (with a simple timer) and without this package, the app started 2sec faster, because we don't create any threads.
After that, I switched to Work Manager and spawn at startup an isolate pool and reuse the isolates for every rest call. This approach is way better, than every time to spawn a new isolate.
Hello, thanks for this handy package! In Readme you're saying that using background compute can be slower. Could you please share sample data / describe in brief your findings?
I assume results heavily depend on particular device and parallelism implementation by different vendors.
But may be you can share some rough data just to know what to expect, like worse case scenarios, severity and share of problem cases you observed.
Thank you!
The text was updated successfully, but these errors were encountered: