On Friday 21 July 2017 13:45:51 Dan34 wrote:
[..]
>
> In short, these could affect my case: SO_RCVBUF, SO_SNDBUF on nginx side and
> whatever buffering nginx uses for handling data. I run that same test with
> 25MB data and I got totally identical result: 12.5MB was buffered on nginx
> side. That
details: http://hg.nginx.org/nginx/rev/230d16d35ebc
branches:
changeset: 7073:230d16d35ebc
user: Roman Arutyunyan
date: Fri Jul 21 19:47:56 2017 +0300
description:
Mirror: "off" paramater of the "mirror" directive.
diffstat:
Hello Valentin,
> 1. Write socket buffer in kernel on node.js side where node.js writes
data.
we can throw this out from equation, as I measure my end time by the event
when socket is closed on nodejs side, (I use http1.0 from nginx to node to
make it simple for this case).
> 2. Read socket
ВНЕЗАПНО в лог начало переть бешенное количество записей OPTIONS (с
кодом 204, если что). Через какое место можно отказаться от их
логгирования?
для location которому соответсвует URL у меня прописанно 'access_log off',
но видимо их логирование идет по другим правилам.
On Friday 21 July 2017 07:02:07 Dan34 wrote:
[..]
> I run nginx on 8080, for testing, since it's not suitable for live use on 80
> in my case and I'm trying to figure out how to fix it.
> And here's why I believe that there is a bug.
>
> In my case, I wrote test code on node side that serves some
> Depending on the compromises you are willing to make, to accuracy or
> convenience, you may be able to come up with something good enough.
I have a more or less working solution. nginx breaks it and I'm trying to
figure out how to fix it.
> Yes. That is (part of) what a proxy does. Even
It looks as if the static content is being served by the Rails asset pipeline
rather than directly by nginx
and the impact is enormous. It took 25s for the base page - but it also took
another 25s for the http://cryonics.org.au/assets/application.js
> X-Accel-Buffering: no
> That will disable nginx's buffering for the request.
At first it looked like exactly what I was looking for (after reading nginx
docs), but after trying I observed that there were no effects from that.
In code that writes headers I added
I advise you implementing - direct file upload.
Read more:
https://stackoverflow.com/questions/44371643/nginx-php-failing-with-large-file-uploads-over-6-gb/44751210#44751210
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,275567,275602#msg-275602