AccuRev Keep - Your Developers Moving Forward! AccuRev Admin’s Real Life Experiences // Long update Sequel

Why is my workspace update taking sooo long? It’s been running for hours…the sequel…

Have you looked at the Operating System’s network interface looking for network collisions? Collisions slow network traffic and in the case of high numbers of collision can bring a network throughput to a crawl as packets can be discarded or sent back to the originator for retry.


Running Linux’s “netstat –ie” or Windows “netstat –ae” and looking for collisions / discards counts. If the network connection is healthy then the count should be zero (0).    If the count is growing then something is amiss in your network or configuration. What could be causing problems? There could be a switch/router/NIC that is misconfigured or going bad.


On Linux

netstat -ie

eth0     Link encap:Ethernet HWaddr 28:d2:44:0b:2f:08
         inet addr: Bcast: Mask:
         inet6 addr: fe80::2ad2:44ff:fe0b:2f08/64 Scope:Link
         RX packets:643179 errors:0 dropped:0 overruns:0 frame:0
         TX packets:410317 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:610567992 (610.5 MB) TX bytes:63247398 (63.2 MB)
         Interrupt:20 Memory:f2500000-f2520000


On Windows

netstat -ae

Interface Statistics
                                       Received                   Sent
Bytes                         2281490326       1855357430
Unicast packets             3660363             2922403
Non-unicast packets                 0                        0
Discards                                      0                        0
Errors                                           0                        0
Unknown protocols                  0


The solution is to have someone from IT/Network admin investigate and fix the problem.

 After the problem is corrected, check once and-a-while to be sure the collisions stay at zero.