Keeping your storage well maintained can help keep your costs low. With dependencies, job files, job logs and rendered images remaining in your account, the amount of space your are using can't grow quite quickly. To help monitor and maintain your storage, the Conductor web interface has a number of tools to help keep it clean.
To access the storage tools, log into the web interface and navigate the left side menu to Storage.
In the Conductor Storage Dashboard, your data is displayed in a responsive circular graph. The graph can be changed to show storage usage by Size, Age or Combined (Size and Age). Size, of course, sorts by the files footprint on disk. Age indicates the amount of time since the file was last referenced. Size and Age combines these 2 factors.
In our example above, you can see there are 2 projects in the account; GWTW and GotG. GWTW (displayed in the graph as the royal blue sections) is consuming 17.5 GB and has been active for 322 days. Project GotG (light blue) is a bit newer at 42 days and currently consuming 5.1 GB.
The graph is set to display by size, the delete age is set to 30 days and there are 10 GB in the Trash.
By mousing over any of the containers within the graph, we get feedback as to amount of storage that container represents. The center circle provides feedback regarding the highest level of the graph in its current state.
With the cursor over the center at "account" level, we see the current consumption of the entire account's storage. After drilling into the the center ring reports Project Storage. Notice we have drilled into project GWTW and it confirms the dashboard level of consumption.
Return to the up the stack by simply pick the center ring.
Drilling into containers
After the center, the next inner ring shows project dependency storage amounts. The outer ring will show job output sizes. Selecting any of the containers in a project opens the the graph to isolate first the project level to display and list the jobs within;
Selecting any of the jobs will isolate that jobs graph to show the files and tasks within.
Here we have access individual files in the job.
To back out of the containers, select the center ring. The Back button of your browser will return you to the Conductor web interface.
From any of the levels of the storage graph; projects, jobs or files can be dragged into the Deletion Staging Area.
Once in the staging area, you have 3 options.
- Trash: The Trash button will delete files and dependencies that are either not being referenced or the referencing file is also being deleted.
- Incinerator: The incinerator will delete files without validating that the deleted files are being referenced elsewhere. Deleting referenced files will have an impact on performance or quality.
- Undelete: Undelete allows users to restore files accidentally dragged to the deletion staging area.
Dragging items to the deletion staging area will populate the values under the trash can and incinerator.
In the example above, we see that the total amount of storage this job deletion will represent is 22.9 MB, 6.9 MB of which are still being referenced by other jobs. If we select the Trash Can, we will free up 16 MB and leave the other 6.9 MB for the other jobs. If we select the Incinerate button, all 22.9MB will be deleted. Either selection will bring up one last confirmation.
If we select I'm Sure!, you will no longer be able to use the Undelete button to restore the entire job.
These are estimates of the amount of storage that will be saved after the files are removed from the account. Deleted files are removed from disk at 11:00AM UTC
Tips and Tricks to using the Storage dashboard.
- Remember to use the center of the graph to return to the next higher level of data.
- Use the checkbox to select multiple projects, jobs or files to drag into the deletion staging area.
- Watch depth of data penetration with the graph guide.
A. Account level
B. Project level
C. Job Level
- Incinerate will definitely delete files from storage and will affect any other jobs referencing them. So please be sure!
- Some files may appear as 0 bytes. These are files uploaded by early versions of Conductor, before we captured size as part of the file's metadata. Uploading files with the latest version of the Conductor app will include file size data.