[GitHub] [incubator-pagespeed-ngx] zz9pzza commented on issue #1380: nginx worker 100% cpu usage (spinning on write returning EAGAIN)

zz9pzza commented on issue #1380: URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1380#issuecomment-763210325 ``` james_@DESKTOP-OTOBGUP:~$ curl -I https://archiveofourown.org/ HTTP/2 200 server: nginx/1.19.6 x-page-speed: 1.13.35.2-0 ``` We are

[GitHub] [incubator-pagespeed-ngx] oschaaf commented on issue #1380: nginx worker 100% cpu usage (spinning on write returning EAGAIN)

oschaaf commented on issue #1380: URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1380#issuecomment-763210833 @zz9pzza seems relevant to this issue, sure. Apparently the tweak to bump the buffer sizes associated to the pipe didn't help in your case, so it sounds like a

[GitHub] [incubator-pagespeed-ngx] zz9pzza commented on issue #1380: nginx worker 100% cpu usage (spinning on write returning EAGAIN)

zz9pzza commented on issue #1380: URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1380#issuecomment-763202036 I am hitting this we think. http://mailman.nginx.org/pipermail/nginx/2021-January/060344.html

[GitHub] [incubator-pagespeed-ngx] urifoox commented on issue #1380: nginx worker 100% cpu usage (spinning on write returning EAGAIN)

urifoox commented on issue #1380: URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1380#issuecomment-763207206 @zz9pzza - did you try to apply the patch / recompile? https://github.com/apache/incubator-pagespeed-ngx/pull/1481