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 Sep 8, 2021. It is now read-only.
What is the performance impact of the new out-of-process/GRPC based approach for function aps hosted in AKS? I assume the performance will be inferior to the in-proc .net core 3.1 azure functions runtime, or?
The text was updated successfully, but these errors were encountered:
how will the overhead of the underlying azure function host vs your app be billed? (when you're paying per second, per MB), starting up functions, then starting a second out-of process host.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What is the performance impact of the new out-of-process/GRPC based approach for function aps hosted in AKS? I assume the performance will be inferior to the in-proc .net core 3.1 azure functions runtime, or?
The text was updated successfully, but these errors were encountered: