App performance is normal WHILE running packet capture
I help support a 3rd party Web application. We have a location experiencing an issue that, while performing a data processing function the web app retrieves and opens data for review and correction processing. Opening this data to process is taking between 30 to 40 seconds to open. When I start/run a Wireshark packet capture using the local loopback interface then launch (all this on the server) and go through the same steps to process the data, it pulls up in 5 to 10 seconds which is considered normal latency for this operation. When I stop the capture, the same delay opening the data returns! We repeated this process getting the same results as before with the 30 to 40 second delay returning after the capture is stopped.
Does anyone have an idea why this is happening? Is there a setting in Wireshark that might be causing this? Is so, is there an option to disable it?
It might help if you add the output of
wireshark -vorHelp->About Wireshark:Wiresharkto the question info. That will include the capture library and operating system info.