I haven't been able to find any definitive explanation on the amount of performance degradation to NTFS.
<hypothetical engineer> So it looks more like hey this isn't necessary and incurs additional I/O let's turn it off. Thanks for your input! Good to know there are others in the same boat. Nile -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Melvin Backus Sent: Thursday, June 4, 2015 12:42 PM To: [email protected] Subject: [powershell] RE: NTFS - Last Accessed Time That sounds reasonable as long as you can replicate the search / results both before and after. We run the last access here and I've not seen any noticeable difference. That doesn't mean there isn't a performance hit, just that we haven't noticed one. :) -- There are 10 kinds of people in the world... those who understand binary and those who don't. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Gilmanov, Nile Sent: Thursday, June 4, 2015 10:03 AM To: [email protected] Subject: [powershell] NTFS - Last Accessed Time Hey guys, We want to enable NTFS's last access time tracking for our file server in order to archive away things people don't use any more. cli> fsutil behavior set disablelastaccess 0 What would be a good way to test performance degradation introduced by one more thing that I/O has to handle? Perhaps: searching through large amounts of folder/file structures and piping that to Measure? Any better ideas? Nile ================================================ Did you know you can also post and find answers on PowerShell in the forums? http://www.myitforum.com/forums/default.asp?catApp=1 ================================================ Did you know you can also post and find answers on PowerShell in the forums? http://www.myitforum.com/forums/default.asp?catApp=1 ================================================ Did you know you can also post and find answers on PowerShell in the forums? http://www.myitforum.com/forums/default.asp?catApp=1
