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
We might as well load and parse the individual components in parallel. Most of the code does not use Federations, so it is thread safe already. When #111 is complete we can revisit and parallelize even more code.
I suspect we can gain some performance improvements here, but we should benchmark the multithreaded implementation to ensure that it is indeed faster (the minor overhead may outweigh the benefits in some cases).
If we can parse/load components very quickly we may even be able to move to a stateless Reveaal where we maintain no state between queries. This allows us to do other parallelization more easily as there is no shared state between queries.
The text was updated successfully, but these errors were encountered:
We might as well load and parse the individual components in parallel. Most of the code does not use Federations, so it is thread safe already. When #111 is complete we can revisit and parallelize even more code.
I suspect we can gain some performance improvements here, but we should benchmark the multithreaded implementation to ensure that it is indeed faster (the minor overhead may outweigh the benefits in some cases).
If we can parse/load components very quickly we may even be able to move to a stateless Reveaal where we maintain no state between queries. This allows us to do other parallelization more easily as there is no shared state between queries.
The text was updated successfully, but these errors were encountered: