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
Describe the performance issue ActorGraphInterpreter Props static method uses Expressions, which has a large perf impact for cases where streams are created in a transient/semi-transient (i.e. stream per actor lifecycle) fashion.
Additionally some stages use this as well, and, per above, we shouldn't.
Data and Specs
See #4698 for details. The benchmarks there illustrate the overall concern well enough.
Expected behavior
Don't use Expression based props where it's possible transient actors are being created.
Actual behavior
We use expression based props and it hurts perf by a significant margin
Environment
N/A
Additional context
This is not as big a problem for single streams created.
This should almost certainly be covered by unit tests, as ActorGraphInterpreter uses a single arg at present and is not touched frequently.
The text was updated successfully, but these errors were encountered:
to11mtm
changed the title
[PERF] ActorGraphInterpreter uses Expression based props
[PERF] ActorGraphInterpreter and other Akka streams internals use Expression based props
Jun 19, 2023
Related to #4698
Version Information
1.4.x
Describe the performance issue
ActorGraphInterpreter
Props static method uses Expressions, which has a large perf impact for cases where streams are created in a transient/semi-transient (i.e. stream per actor lifecycle) fashion.Additionally some stages use this as well, and, per above, we shouldn't.
Data and Specs
See #4698 for details. The benchmarks there illustrate the overall concern well enough.
Expected behavior
Don't use Expression based props where it's possible transient actors are being created.
Actual behavior
We use expression based props and it hurts perf by a significant margin
Environment
N/A
Additional context
This is not as big a problem for single streams created.
This should almost certainly be covered by unit tests, as
ActorGraphInterpreter
uses a single arg at present and is not touched frequently.The text was updated successfully, but these errors were encountered: