Reply to thread

Message

<blockquote data-quote="danb" data-source="post: 956829" data-attributes="member: 62850">I renamed some of the new options so it makes sense... you will see <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite110" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />.I actually read that article (or one very similar) while while researching which features to add, and truly that might have made sense like 10-20 years ago.&nbsp; But now with multicore processors, I am certain the difference is negligible.&nbsp; I need to look into this feature a little more, but if the process is only identified by path, and not hash, then we for sure need this feature.&nbsp; If MD also identifies the file by file size, that would certainly be better than simply identifying by path, but either way I think this is a worth while feature, and one I might add to some of the profiles as a standard / recommended option.&nbsp; We can play around with it and see if it really does show a performance hit... I highly doubt it does.&nbsp; I have been playing with these types of things for 10 years now, so I have a pretty good idea how long it takes to calculate a hash on a file <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite110" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />.&nbsp; Thank you!</blockquote>

[QUOTE="danb, post: 956829, member: 62850"] I renamed some of the new options so it makes sense... you will see ;). I actually read that article (or one very similar) while while researching which features to add, and truly that might have made sense like 10-20 years ago. But now with multicore processors, I am certain the difference is negligible. I need to look into this feature a little more, but if the process is only identified by path, and not hash, then we for sure need this feature. If MD also identifies the file by file size, that would certainly be better than simply identifying by path, but either way I think this is a worth while feature, and one I might add to some of the profiles as a standard / recommended option. We can play around with it and see if it really does show a performance hit... I highly doubt it does. I have been playing with these types of things for 10 years now, so I have a pretty good idea how long it takes to calculate a hash on a file ;). Thank you! [/QUOTE]

Verification