![]() ![]() Here's how long my Surface Pro 4 (Core-i7 256GB SSD) takes to extract Firefox's source tarball on Windows: you should also see that it now only takes < 3 mins (depending on your hardware) to extract the archive above. This improvement was deployed live by the Defender team last weekend, so if your machine is up to date with its Defender signatures, etc. The team implemented and tested a fix in their signatures & scanning engine, adding tar to the same heuristic, and extraction of the test case - Firefox's source archive - dropped from ~31 mins to ~3 mins! wherein it defers scanning of the extracted files until after the extraction completes. This was somewhat surprising since Defender already has special-case heuristics for archiving tools like 7Zip, WinZip, etc. It turns out that Defender was synchronously scanning each file as it was extracted, significantly impacting tar's ability to extract files quickly. Last week, I shared this issue with Defender, IO, and NTFS partner teams and we worked together to repro, measure, trace, and analyze the issue with tar taking far longer than expected to extract a large source archive on Windows. and the fix we deployed during last weekend! What we did I have just edited the title of this issue to accurately reflect the reported issue. Windows & Linux (WSL2) tests were run on a Surface Book 1/core i5/8gb/256gb SSD.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |