The curious case of slow downloads

You're correct, but the title is way less helpful without the "nginx". Unless the reader knows that cloudflare uses nginx, he won't know the article pertains to nginx

Re: The curious case of slow downloads

#5

Post by oarsinsync » Wed, May 04, 2016, 12:18 PM UTC

Dylan16807 wrote: post #3

speps wrote: post #2

Original title doesn't mention "NGINX".

Context in a title is useful.

> Not an NGINX problem either

Re: The curious case of slow downloads

#6

Post by Dylan16807 » Wed, May 04, 2016, 12:20 PM UTC

oarsinsync wrote: post #5

Dylan16807 wrote: post #3

Earlier quoted context omitted.

Context in a title is useful.

> Not an NGINX problem either

There is a header that says that, but it actually was an NGINX problem.

Re: The curious case of slow downloads

#7

Post by bigethan » Wed, May 04, 2016, 12:24 PM UTC

This is why open source (and controlling your whole stack) matters in big business.

For example, Microsoft may be changing their image, but their core software is closed source. may be great, but can you pull off something like this when you've got an issue? The importance of being able to debug and patch your mission critical systems is hard to overstate.

Please encourage your employer to fiscally support the open source code that they rely upon!

Re: The curious case of slow downloads

#8

Post by masklinn » Wed, May 04, 2016, 12:25 PM UTC

gruez wrote: post #4

speps wrote: post #2

Original title doesn't mention "NGINX".

You're correct, but the title is way less helpful without the "nginx". Unless the reader knows that cloudflare uses nginx, he won't know the article pertains to nginx

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].

Re: The curious case of slow downloads

#9

Post by masklinn » Wed, May 04, 2016, 12:27 PM UTC

Dylan16807 wrote: post #6

oarsinsync wrote: post #5

Earlier quoted context omitted.

> Not an NGINX problem either

There is a header that says that, but it actually was an NGINX problem.

Not really. nginx's implemented behaviour seems more or less what anyone writing socket code would do: write to buffer, then wait with timeout to write more, if timeout is hit consider the write failed.

The problem here is that (TIL) on linux the "writable socket" state behaves completely differently than the "readable socket" one, and a socket can be effectively writeable even though poll(2) reports that it isn't.

Re: The curious case of slow downloads

#10

Post by masklinn » Wed, May 04, 2016, 12:31 PM UTC

bigethan wrote: post #7

This is why open source (and controlling your whole stack) matters in big business. For example, Microsoft may be changing their image, but their core software is closed source. may be great, but can you pull off something like this when you've got an issue? The importance of being able to debug and patch your mission critical systems is hard to overstate. Please encourage your employer to fiscally support the open s…

> For example, Microsoft may be changing their image, but their core software is closed source. may be great, but can you pull off something like this when you've got an issue? The importance of being able to debug and patch your mission critical systems is hard to overstate.

Not OSS != no source access. A cloud provider on top of the MS stack would most likely have Shared Source Initiative licenses.