Dec 29 2009, 10:43 PM
QUOTE(mj_MohSen @ Dec 29 2009, 09:02 PM)
I'm not Malaysian and I complain, when there's reason to do so.
Unacceptably slow here in Bukit Puchong, they used to have this excuse of maintenance until Dec 24th. almost all good services (facebook, youtube, RS) are throttled. now what?
Speaking of maintenance, let me share something with LYN community that i just found out about. Basically i created a thread at helpdesk asking why LYN was down today and after reading the explanation by se7en and cascading failure, i think i found out the reason why we are facing slow connections every time TM is doing maintenance, the same reason why LYN went down todayUnacceptably slow here in Bukit Puchong, they used to have this excuse of maintenance until Dec 24th. almost all good services (facebook, youtube, RS) are throttled. now what?
Sometimes, when a node or server is taken down for maintenance (non functional, which is equivalent to a failure), it can cause massive network load problems which i believe is the cause of all the slowdowns when " network maintenance " is done by TM due to their lack of knowledge or "tidak apa" attitude when performing such actions...
QUOTE
The animation shown here illustrates an example of a connecting node between a local ISP and their Internet backbone being overloaded.
Initially, the traffic that would normally go through the node is stopped. Systems and users get errors about not being able to reach hosts. Usually, the redundant systems of an ISP respond very quickly, choosing another path through a different backbone. The routing path through this alternative route is longer, with more hops and subsequently going through more systems that normally do not process the amount of traffic suddenly offered.
This can cause one or more systems along the alternative route to go down, creating similar problems of their own.
Also, related systems are affected in this case. As an example, DNS resolution might fail and what would normally cause systems to be interconnected, might break connections that are not even directly involved in the actual systems that went down. This, in turn, may cause seemingly unrelated nodes to develop problems, that can cause another cascade failure all on its own.
Initially, the traffic that would normally go through the node is stopped. Systems and users get errors about not being able to reach hosts. Usually, the redundant systems of an ISP respond very quickly, choosing another path through a different backbone. The routing path through this alternative route is longer, with more hops and subsequently going through more systems that normally do not process the amount of traffic suddenly offered.
This can cause one or more systems along the alternative route to go down, creating similar problems of their own.
Also, related systems are affected in this case. As an example, DNS resolution might fail and what would normally cause systems to be interconnected, might break connections that are not even directly involved in the actual systems that went down. This, in turn, may cause seemingly unrelated nodes to develop problems, that can cause another cascade failure all on its own.
^doesn't that sound familiar?
This post has been edited by andrew9292: Dec 29 2009, 10:58 PM
Quote
0.0240sec
0.43
7 queries
GZIP Disabled