LucidLink is a distributed file system for object storage, allowing you to stream, and get on-demand file system access to object storage, as if it were a local disk. 

When running on your system, LucidLink stores cache and metadata locally. The cache data is used to store frequently accessed data as well as data still in-flight. The metadata is used to create the file system folder structure, the file system index if you will. These are pointers to where in the object storage the data is located.

The location where cache and metadata is stored is configurable. By default this is part of your user home directory %userprofile%\.lucid on Windows or ~\.lucid on macOS or Linux. 

Note that on Windows, if you are running LucidLink as a service this default location is C:\Windows\system32\config\systemprofile\.lucid. Moving this folder will require UAC elevated permissions.

If you are using the LucidLink application or have LucidLink running as a service it may be best to to move your .lucid folder to a new location and re-point to this folder using a symbolic link or perform this operation before launching LucidLink and joining your Filespace.

On Windows, after moving the .lucid folder, run (under a UAC elevated command prompt):

mklink /d <original-location>\.lucid <new-location>\.lucid

On macOS and Linux, after moving the .lucid folder, run:

ln -s <new-location>/.lucid <original-location>/.lucid

If you are using the command line or terminal to run LucidLink from end-to-end and will not be using the LucidLink Client user interface, you can simply change where the cache and metadata is stored by using the `--root-path` flag.

Link to your Filespace with --root-path option:

lucid3 daemon --fs <filespace.domain> --user <user> --password <password> --mount-point <mount-point> --root-path <path>

To adjust your cache size. Please consult Adjust local cache settings

Use cases are increasing your cache for applications or workflows which would benefit from a larger default cache of 5GB.