You can imagine this leaves us kind of buffeled since we cant understand how starting wireshark to debug a problem actually solves it. now we found out, that when we only start dumpcap in a cmd window the same effect happens: no performance issues. We can close Wireshark, restart the IIS Webservice, disable / enable the network connection, the performance issues does not appear anymore until we restart the OS of the Webserver.
so we tried if we can find something by capturing some LAN traffic with Wireshark, then something unexpected happened: when we start Wireshark on the web server (Win 2012 R2), the performance issue instantly disappears. we checked network settings on our Cisco switches, web server configuration, SQL server configuration, OS settings, logs and so on but we could not grip where the problem is coming from. We have a performance issue with our intranet website. I wanted to post this question, since i saw someone already has the same problem i post this here, maybe some usefull information: Since I'm not very fund of reading source code I was wondering if any of you guys can tell me what is done on the Windows network side while starting WireShark or if you might have any hints regarding this. It seems that during the start of WireShark something is changed/reinitialized on the Windows networking parameters. Opening and closing WireShark again is then bringing the VM network speed back to it's high performance.
Now the cool thing is that starting WireShark and closing it again and then using the database client application suddenly everything is very fast! This performance improvement stays there until the VM is restarted. For troubleshooting reasons I installed WireShark as the loading performance was not sufficient. Using a database client application it takes a x amount of time to load the data from the db to the VM.
Dear WireShark Team, I have a very interesting behavior on some VM's installed with plain Windows 2012 R2 Server using PVSCSI and VMXNET3 drivers on vSphere 6.
0 kommentar(er)
