-
Notifications
You must be signed in to change notification settings - Fork 695
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid offload() log messages #80
Comments
fixed (or better, 'improved') in 1.9 |
I'm getting proper HTTP status code, but message is logged immediately and shows 0 msecs, shouldn't this be logged by offload thread itself once it finishes sending file? |
To have proper time reporting for offloaded request, we would have to: it's very very unimportant for me |
I've created new milestone "Future Ideas" to track such feature requests |
This is an interesting problem, as offloading is becaming present in more and more areas. For proxy offloaders (http, uwsgi) the backend node will log normally, so the information is not lost. Response offloaders (cache, and the new 'offload' transformation) refers only to data transfer time (as well as sendfile()), so we need to evaluate if such information is relevant (considering kernel buffering all over the place) to a level needing a new logging category. |
I don't care for upload time for static files so let's close it |
7 msecs
this file is big (~600MB) so it wasn't fetched so fast, this is probably the time between request start and sending it to offload thread(HTTP/1.0 -30)
- since offload is taking care of this file, than I think it's safe to just hardcode it to 200 (or 304 if static offloading takes care of that)The text was updated successfully, but these errors were encountered: