Skip to main content
Solved

Has anyone else experienced antivirus interference with DQ Analyzer 11?


Forum|alt.badge.img+1

My organization runs McAfee antivirus.  I’ve just tried out the DQ Analyzer 11 tool and really like it, but it takes forever to start up or perform any actions.  Just starting up, the antivirus pegs 1 CPU for about 30 minutes before the application starts.  And then various actions like starting a new profile or clicking a menu item will also be delayed by several minutes at least.

We’ve tried excluding the install directory, but it hasn’t helped.  Any ideas?  Has anyone else run into this issue before, and how did you solve it?

 

Best answer by chandankaushal

Hi Justin,

We have tested this on our end and everything seems to be working fine. We do not have any issues with the performance of DQA. As I can see from the screenshot that you Antivirus is already using 24% of your CPU so it might be the cause of the performance issues with DQA. Can you contact your security team and test it while the antivirus/constant-scan feature is turned off?

Thanks,
Chandan

View original
Did this topic help you find an answer to your question?

2 replies

Forum|alt.badge.img

Hi Justin,

We have tested this on our end and everything seems to be working fine. We do not have any issues with the performance of DQA. As I can see from the screenshot that you Antivirus is already using 24% of your CPU so it might be the cause of the performance issues with DQA. Can you contact your security team and test it while the antivirus/constant-scan feature is turned off?

Thanks,
Chandan


Forum|alt.badge.img+1
  • Author
  • Data Voyager
  • 1 reply
  • August 31, 2022

Thanks for the replace Chandan.  The antivirus at 24% is because I had just launched DQA.  The antivirus stays at that level until the app finishes launching, around 30 minutes later.  Then, clicking on a menu option triggers the antivirus again and causes DQA to go into “(Not Responding)” status.  It stays around 25% for a few minutes, then back to 0% once DQA responds again.  They are most definitely correlated, so I was just curious if anyone else is running enterprise-wide McAfee and what they have done to exclude DQA from it.

We will continue testing and trying things on our end.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings