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 Feb 22, 2022. It is now read-only.
Essentially doing this: https://blog.mavnn.co.uk/logging-freya/
and finding that adding the composition affects every request - it takes a significant CPU hit (response time going from ~20ms to ~300ms). Tests indicate that it's something in the composition itself, as injecting the value into the freya state takes no time at all.
I'm guessing there is a way to optimize this. Glad to know I'm not crazy. I found this same issue in the past but didn't have time to figure out why it was so bad.
et1975
changed the title
>?= (Pipline.compose) on freya<PipelineChoice> and freyaRouter causes significant delay in every request
>?= (Pipeline.compose) on freya<PipelineChoice> and freyaRouter causes significant delay in every request
Oct 31, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Essentially doing this: https://blog.mavnn.co.uk/logging-freya/
and finding that adding the composition affects every request - it takes a significant CPU hit (response time going from ~20ms to ~300ms). Tests indicate that it's something in the composition itself, as injecting the value into the freya state takes no time at all.
Sample code:
Wondering if I'm doing it wrong, or maybe there's a way to optimize that away.
The text was updated successfully, but these errors were encountered: