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
Is your feature request related to a problem? Please describe.
Seems that ring has a way to avoid passing a file through the handler if it exists https://github.com/ring-clojure/ring/wiki/Static-Resources. If we can use wrap-file on the code, we will save a lot of CPU resources since the request will avoid all of our handlers (and most probably the transmission will also be way faster)
Describe the solution you'd like
Implement wrap-file function for sending our css and js files
Describe alternatives you've considered
None
How important is this feature to you?
I have a strong feeling that this is the reason why Metabase takes 30 seconds on my 100MB symmetric connection to send a 6MB file from the US
Additional context
I don't know if this has any collateral damage, it should not I guess since statics are always the same (we just send the ones for embedding in case we detect that the user is going through that flow, but that shouldn't cause any weird scenario)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Seems that ring has a way to avoid passing a file through the handler if it exists https://github.com/ring-clojure/ring/wiki/Static-Resources. If we can use wrap-file on the code, we will save a lot of CPU resources since the request will avoid all of our handlers (and most probably the transmission will also be way faster)
Describe the solution you'd like
Implement wrap-file function for sending our css and js files
Describe alternatives you've considered
None
How important is this feature to you?
I have a strong feeling that this is the reason why Metabase takes 30 seconds on my 100MB symmetric connection to send a 6MB file from the US
Additional context
I don't know if this has any collateral damage, it should not I guess since statics are always the same (we just send the ones for embedding in case we detect that the user is going through that flow, but that shouldn't cause any weird scenario)
The text was updated successfully, but these errors were encountered: