Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

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

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
0 0 925

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:192.168.49.205 Bcast:192.168.49.255 Mask:255.255.255.0
         inet6 addr: fe80::2ad2:44ff:fe0b:2f08/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
         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.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.