|
|
Question : Problem: how server upload speed effects the client?
|
|
if my server got a internet line with 12kbyps and i will pgrade to 128kbyps will my clients feel the diffrence between html pages of take 20kb?
|
Answer : Problem: how server upload speed effects the client?
|
|
If we go with averages on average you will have
1.6 wap per second (100 users at 1 request per minute each = 100/60) 0.9 web per second (50 users at 1 request per minute each = 50/60).
1.6 mobile request will generate 24 KB of traffic and .9 "regular" requsts will generate 90KB. This means that in order to provide "1 second" response time you need to be able to handle 114KB ps of traffic. Accouting for some overhead you need about 1,000 Kbps (1 Mbps) connection in order to handle that load with an average of 1 second response time. Anything less will start cauing a backup.
At 512 Kbps you can only serve up about 57 KB ps. So the 1st set of requests will take 2 seconds, but at the start of the 2nd second, you get a new set of requests that adds load. With basically 114 KB of request coming in every second, you will fall way behind soon.
Again another option is to enable dynamic HTML compression. Assuming your pages are mostly text this could yeild about 70% (or greater) compression. Which means instead of attempting to send out 114 KB of data you are actually only sending out about 35KB of data, which a 512 KBps link could handle.
|
|
|
|