![]() More soon.Įdit #4: The test of a 64-bit build of WinDirStat was successful. WINDIRSTAT VS FULL VERSIONIt may not work for the original question if the drive contains 6+ million files.Įdit #2: Full version of WinDirStat crashes at 10 million files and 1.9GB usedĮdit #3: I got in touch with the WinDirStat developers and: (1) they agree that this was caused by memory usage limitations of the x86 architecture, and (2) mentioned that it can be compiled as 64-bit without errors. The fact that the server in question has only 2GB of RAM may be problematic in this specific case, but most servers with such large numbers of files will have much more RAM.Įdit #1: I regret to have discovered that, when tested on a 4TB volume containing millions of files, WinDirStat Portable crashed after indexing about 6.5 million files. ![]() The standard 32-bit build is limited to 10 million files and 2 GB RAM usage, but the source code will build successfully as a 64-bit application. Click on any item in the visualization and you'll see it in the directory tree. That gives it more memory to work with but I'm not sure if it's going to be enough unless they can persist to disk.ĭefinitely try WinDirStat: it gives a fantastic visualization of disk use by depicting each file as a rectangle drawn to scale, color coded by file type. WINDIRSTAT VS UPDATEUpdate #2: Looks like the developers of WinDirStat got involved enough to tell us that it can compile under 64-bit. This tends to run out much too quickly with 18,501,765 files and 7,142,132 folders. Update #1: The server I am attempting to analyze has 2 GB of RAM and most products that I try seem to try and keep the file/folder information in memory.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |