0

Cleaning up things after a MB crash, I got a Samsung NMVE 2 (1TB) drive and did transfered Windows 10 64 bits from a SATA SSD to it (in a 500GB partition), and really helped to load OS and some Apps, like Chrome with 20 tabs, for example.

Problem: for Visual Studio development solutions, Office (64) Docs and pdfs it did not help a lot...

I have 500GB available in another partition of Samsung NMVE 2, but My Documents folder has almost this size, and I really want to speed up only those cited above, that weight around 100GB. For several reasons I do not want to have a My Documents folder in two drives letters.

My Documents folder is located in a bigger and slower SATA 6 drive, NAS series, with 5600 RPM...

So, any tips, drawbacks, problems anticipated in this strategy: put symlinks in the original slow drive pointing to the faster NMVE? It will slow a lot the loading from NMVE?

Of course, any other strategy to suggest?

TIA

9
  • 2
    No, that's basically what I would do. If it is your entire My Documents drive, you can just go to properties, location, and change it there, then say move all files to do it for you. easier than symlinks
    – LPChip
    Dec 15, 2020 at 15:55
  • @LPChip: in this case I'll test both strategies in a couple folders and do a benchmark just to confirm that there is no strange result or discrepancy - who knows? - and I'll post here. Thanks. Dec 15, 2020 at 16:09
  • This is EXACTLY what I do.. only I use folder junctions and not symlinks. I also do the opposite and put BIG JUNK (like symbols or rarely used sdks) on the slow drive and link back to the fast one to save precious FAST space. Dec 15, 2020 at 16:25
  • @SeñorCMasMas: after your comment I saw this and this but could not figure out one big reason to use folder junctions instead. Could you elaborate more? Dec 16, 2020 at 3:03
  • 1
    OH.. also, @LPChip is a smart cookie (pun intended).. I also find that changing the actual directory the explorer will use is easier. The only problem with this method is that SOME DEVS are too lazy or too stupid to ask the win32 API where the documents folder is located and make assumptions. Dec 16, 2020 at 18:15

0

You must log in to answer this question.