Managing Hard Disk / Solid State Disk space.

Hey i have some question about how to correctly set up my files structure.

In my setup i have 3 disks:

  1. SSD for OS and applications.
  2. NVMe for poroject files.
  3. 2x HDD as /temp for apps, /VaultCache for UE, and overall files storage.

Is it a good aprouche or should i change some thing for some reasones or to get better performace ?

Disk usage looks fine to me. Might be worth investigating how much a repository (version control) affects the lifetime of your SSD disks if you plan to write GBs of asset data often. For me HDDs are fast enough to work with large git repos but for editor loading times and VS compilation HDD should be noticable slower compared to SSD.

1 Like

Thanks for taking Your time to answer.

From what You say it seems like i can stick with my setup.

I have some other question and maybe You can clear it out for me.

Lets take a CitySample project as a example.

This project is ± 100GB in size.

I have install it on my NVMe disk, but i found out that it is alsow storaged in VaultCache whitch is on my HDD.

So the question is:

Does having VaultCache on slower disk (HDD) affects on how does project perform whitch is on NVMe disk ?

Does VaultCache is used while working on a project or is it only to recall some assets when needed or maybe it works diferently ?

As far as I know Vaultcache works like this:

  1. Product from marketplace is downloaded into VaultCache.
  2. When you click “add to project / create project / install to engine” from the vault, the downloaded files are copied to either the engine or a project.
  3. Vault product remains unused after this point and can even be deleted.