Antivirus is always a good place to start on troubleshooting inexplicable delayshttps://twitter.com/dietrich/status/963470291824357376 …
It's constant space per-file. Just a generation counter for latest definitions the file was checked against, reset to zero on any write to the file. Read where counter != latest triggers scan.
-
-
The average system nowadays has tens of thousands - often hundreds of thousands of scannable files. (It's one of the reason why practically no user does "full disk scan" these days, unless infection is suspected, BTW - takes too damn long.)
-
Even the smallest file takes considerably more disk space than its length in bytes. If you keep the info in separate files, or in streams, you're going to waste a lot of disk space and you're going to have users screaming what these files/streams are.
-
InVircible used this approach (for integrity data) in the 90s. It's been essentially dead as a product for many years. (Thank goodness; it was crap.) As I said, whatever you can come up with - we've tried it before and it didn't work.
-
And if you put the data in a single database, you'd also have overhead managing the database and even just reading from it. And most of the time it will be for naught, because it won't save you a scan.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.