Quote:
Originally Posted by Sephiroth
There should always be 100% signal.
|
Too loose a statement. 100% of what?
Quote:
|
You're nit picking again.
|
I'm nitpicking?! Your entire participation in this thread has been nothing
but nitpicking.
You're arguing about un-noticeably minute amounts of loss on somebody else's connection while your own connection is suffering far more corruption. Shouldn't you be off complaining to VM about your "unacceptable" levels of packet loss which "must" be "service affecting" because it's ten times higher than Jon22's?
Here's a few articles you might want to read in order to get clued up on the sort of applications that really cannot tolerate
any packet loss:
http://www.fragmentationneeded.net/2...own-is-up.html
http://etherealmind.com/myth-fibrech...er-token-ring/
http://packetpushers.net/dont-drop-t...rust-ethernet/
---------- Post added at 22:58 ---------- Previous post was at 22:48 ----------
Quote:
Originally Posted by Jon22
Not at home to check at the moment but that amount of packet loss is something new. Don't usually see that much on the graph. Appears to of stopped anyway.
|
That level of packet loss is the kind that would start affecting your service. The remaining 23 hours or so of your chart looks perfectly fine, and shows a normal error rate that is completely non-service-affecting.
Any slowness or issues you notice with Netflix - unless during periods of high packet loss like between 5:30 and 6:15pm above - are due to something unrelated, e.g. congestion, and not receive errors.