Search the Community
Showing results for tags 'size'.
So I'm looking at getting my art team off of Unity Collab and onto Plastic Gluon for managing and sharing our art assets, and as part of my quick guide doc that I'm putting together, I mentioned that we should remove any folders that we're no longer working with, in order to reduce the size of our repo in the cloud and thus reduce the cost of our plastic membership. Then i realized that because you can un-delete files, that the revisions before the deletion must still be stored in the cloud, so deleting them does nothing for cloud repo size. for non-cloud edition plastic, I've seen the recommendation to use the archive command, but there doesn't seem to be an alternative for Cloud Edition. is there any way to remove files from version control in the cloud in order to reduce our cloud usage for a particular repository? Thank you!
Hello, I wounder if there is any way to reduce or compact the size of Jet database, we are using PlasticSCM for 5+ years now, and it is really great, but we are facing the issue with big database size. I was trying to workaround this issue using either: archive command or distributing database files on more than one hard drive 1- Archive command I read about the 'archive' command as the documentation says it is used to reduce the size of the database, so correct me if I am wrong what is the use of 'archive' command? Here is the documentation about archiving But I could not find any help regarding 'compact' command for Jet database 2- Distributing database on multiple hard drive Is there any way to specify hard drive per repository? or maybe specify multiple hard drives then using some rules if the first drive is almost full the database will start using the secondary drive and so on I also thought about using 'hardlink' (symlink) but I am not sure if that has a side effect on integrity or performance of Jet database Related post: Thanks,
Hi, So my team has been using a repo to push different builds for different projects and have run out of space on the drive we're using. We unfortunately just had everything on separate branches in a deployment repo. Since we don't really need the builds anymore is there an easy way to clean this up? We can't hard delete branches and I'm not sure what's going on with the blobs but that is where all the memory is taken up. Is there anything we can do about that?