2 ms·
Is it now? nginx seems to have pretty normal behaviour here, so the core issue is write-polling buffers on linux rather than nginx itself. It seems to me nginx
by masklinn 11y ago
Is it now? nginx seems to have pretty normal behaviour here, so the core issue is write-polling buffers on linux rather than nginx itself. It seems to me nginx was the messenger of sorts, but the issue doesn't really pertain to nginx.
In a nearby comment, LoSboccacc notes that they've hit that issue [removed: on S3].
- ParadoxOryx 11y agoIt sounded to me like LoSboccacc's solution was to serve files from S3, not that they experienced the same issue on S3.
- masklinn 11y agoYou're right, I misread it.