Welcome! Log In Create A New Profile

Advanced

How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Paul Schlie
June 24, 2014 02:52PM
I've noticed that multiple (as great as 8 or more) parallel redundant streams and corresponding temp_files are opened reading the same file from a reverse proxy backend into nginx, upon even a single request by an up-stream client, if not already cached (or stored in a static proxy'ed file) local to nginx.

This seems extremely wasteful of bandwidth between nginx and corresponding reverse proxy backends; does anyone know why this is occurring and how to limit this behavior?

(For example, upon receiving a request for example small 250MB mp4 video podcast video file, it's not uncommon for 8 parallel streams to be opened, each sourcing (and competing for bandwidth) a corresponding temp_file, where the upstream client appears to being feed by the most complete stream/temp_file; but even upon the compete file being fully transferred to the upstream client,the remaining streams remain active until they too have finished their transfers, and then closed, and their corresponding temp_files deleted. All resulting in 2GB of data being transferred when only 250MB needed be, not to mention that the transfer took nearly 8x longer to complete, so unless there were concerns about the integrity of the connection, it seems like a huge waste of resources?)

Thanks, any insight/assistance would be appreciated.

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Paul Schlie June 24, 2014 02:52PM

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Maxim Dounin June 24, 2014 06:38PM

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Paul Schlie June 24, 2014 07:52PM

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Maxim Dounin June 24, 2014 08:32PM

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Paul Schlie June 24, 2014 09:00PM

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Paul Schlie June 24, 2014 11:00PM

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Paul Schlie June 30, 2014 08:46PM

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Paul Schlie June 30, 2014 09:16PM

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Maxim Dounin June 30, 2014 09:34PM

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Paul Schlie June 30, 2014 11:12PM

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Maxim Dounin July 01, 2014 07:04AM

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Paul Schlie July 01, 2014 08:46AM

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Maxim Dounin July 01, 2014 09:22AM

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Paul Schlie July 01, 2014 10:18AM

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Maxim Dounin July 01, 2014 12:42PM

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Paul Schlie July 01, 2014 04:14PM

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Paul Schlie July 01, 2014 05:04PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 105
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready