improving the perfomance of the process lookup and expanding the deviceBlacklist#1467
improving the perfomance of the process lookup and expanding the deviceBlacklist#1467mncrftfrcnm wants to merge 4 commits into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1467 +/- ##
==========================================
+ Coverage 52.35% 52.36% +0.01%
==========================================
Files 266 266
Lines 14560 14562 +2
Branches 1600 1598 -2
==========================================
+ Hits 7623 7626 +3
Misses 6634 6634
+ Partials 303 302 -1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Thanks for your contribution, it is much appreciated! We'll review it in the upcoming days and report back here. |
There was a problem hiding this comment.
While in theory a correct improvement for large data sets (>100), it is in practice resp. especially here with in almost all use cases less than 10 total windows completely negligible. Thus, please revert the code to its original state.
dbuechel
left a comment
There was a problem hiding this comment.
Thank you very much for the contribution, it is much appreciated. Please review the comments and provide the additional information resp. changes required, and then we can gladly merge the changes into the master branch.
There was a problem hiding this comment.
I suppose this improvement has been suggested to you by an AI? And regardless of that, did you actually measure whether your code in practice improves the execution time required for the process monitoring?
If you would have, then you'd realize that for the somewhere around 100 - 300 normally running processes on a Windows machine, this code will often provide no improvement or even a worse performance due to the additionally required allocation of the hash sets vis-à-vis the fail-fast implementation of the LINQ list traversal. Thus again, please revert the code to its original state or then provide clear evidence that the new code is significantly better performing.
There was a problem hiding this comment.
Have you thoroughly tested all of the new devices in the blacklist? We unfortunately had quite a few issues with false-positive detections when we updated resp. added new devices to the blacklist in the past.
|
Could you please provide feedback on why you closed the pull request? The improvements in the process factory as well as the device blacklist are perfectly valid and can gladly be merged if so requested. |
The previously used dictionaries search was not effective, and use some O(n^2) scans
Also added more virtual devices to blacklist