-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 David,
On 9/11/13 1:48 PM, David kerber wrote: > On 9/11/2013 1:38 PM, Arun Kumar wrote: >> Hi >> >> We are developing small video hosting application ,we are not >> writing any special program for open the video file and send to >> player , simply we are using tomcat DefaultServlet for above all >> video request , now we have to benchmark our application for >> following scenario >> >> 1) video size 100MB (1080i HD) 2) Total Network bandwidth 10Mbps >> (IN/OUT) >> >> >> Now how to calculate how many max thread is allowed for above >> scenario ,with out interrupting users viewing experience, here >> each video response should secure 400kbps bandwidth for no >> interruption >> >> So my question is how many concurrent users can view videos >> without interrupt then how to test this scenario ,and how tomcat >> is handling bandwidth sharing across the request > > Tomcat doesn't do any bandwidth sharing internally; that's up to > your OS and network infrastructure. Basically divide your network > bandwidth's slowest point (probably the ISP connection) by the 400k > you say you need per connection. That is the number of > simultaneous connections you should be able to support, assuming > your server hardware can handle it (which it probably can). There are lots of other factors to consider as well. A naive client might download the entire movie before playing it. Disconnects might end up higher than zero, so the client will have to tr-try and -- it being a naive client -- might just re-start from the beginning. A smarter client might be able to do a HEAD request to get the file size and then use separate requests for chunks of a single file. If the client thinks its being smart (but is really dumb), it might request those chunks simultaneously "to improve performance". If your 400kbps requirement per connection is well-researched and correct, then you can handle: (X bandwidth in kbps) / (0.7 * 400 kbps) The 0.7 factor is a rough estimate of network "waste" chatter required to actually communicate. For example, if you have a 100Mbps connection, you can't actually communicate data at that speed: the connection supports bits moving at that speed, but there is more data flying around than the data your application cares about. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJSMLKwAAoJEBzwKT+lPKRYMDYP/3/7JJFMhcuMDnNJrXYsXvVX wJdMX8HYz/3I0ZbEcND9aFwqBWqeXj3aVU/30KLdHBFehmznvuyBu6o6T0LZyZKI h7bv+m5xCbY5w8DcoLV+juLRevfDhztDLR0dfdw7b1ge7uiSTx/jEQJskgg5EpCG rzZP+jEyeF+0jndzcqc9TFJ14goAz+/osbT6YlYKTiQUwtvRf+hccohQVfo+8THx 4n3apAVHuTn+1mxfjGxfVSvJN/Uoog6014ijNtpQucfltM/zeCrFA6YWrnJblV9t ub1mXRG42SKoeFXl4G2ofC0KNWkgjP2ptYs4gGSd+zvXyK8iUHQ/xeEr2oc10P00 NNuJHf30rDvHzjFUtyABPhTEWOavyWaD80gl03nGIlmxbY5vNGpTn79Ni8ARsmJN qn3LQi4oznwlnuF/EcrePu68HrSIW+iC7ea2FInrzfdolqYm0mJl4J3zQUlZtNek /8dL00JuyWPhjnzziZLywM0hK7SzFgcDW/Z6917hohM/cPtDJbYThNFdbN1nTpml 4XiY+ks86EsUdVpHHVMFXamdXKCmMYezNE3lSMXLntzKacKekFCvbGDV53Jzpeiq a6/JUGm9GZ+UuWeDBwTSe6r7daz/8NO0D1naoYyBz7IU40geADDwwJUg1fcSgYTy LmMnZHqISorvpc7p4GOf =34FV -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
