Rikore wrote:Suggest trying a 4 TB external, they are not that much.
Gave this a try on a separate machine just to test using a WD Passport Ultra, in this specific example I was indexing the .e57's in recap. Probably not a viable solution for us moving forward, unless it was just this specific test but it took 19 hours to index 120GB file running USB 3.0. Pretty good machine as well, i7, 1070 card, 32GB ram, m.2 SSD for operating drive, etc. But I do agree they are cheap and a flexible option. Thanks for the suggestion, you guys clearly have some large files!
imcid953 wrote:I'm not working with Cyclone (using Scene), but our computer has 2 1-TB SSDs set to a raid 0.
Have you benchmarked this setup against running a 1TB m.2 Samsung 950/960 Pro?
I posted this on February 15, 2017
10TB, 12TB, 14TB HELIUM FILLED HDD & INFINIBAND
From the last 3 months of use, the two Helium 10TB Seagate SAS Raid 6 systems (100TB each) we built are almost as fast as SATA SSD Raid XX systems, but significantly cheaper, especially if you need to be in the 100TB and larger storage capacity.
Dennis this is awesome and I can't wait to have these kinds of storage issues in the near future, something to start thinking about as a long term setup
Phil Marsh wrote:
Cant you just have Cyclone and database installed on your SSD but have your working directory on an additional internal hard drive. This is where the 4x times space things comes in for unifing, etc.
Thanks for the suggestion Phil, I tried doing this exact workflow with a number of configurations as we have a few different drives to choose from. The most promising was like you said running cyclone and database from the 1TB SSD completely empty and setting the working drive to an open 4TB WD Black. However I still got the same space errors or what I believe to be space errors (I never got a firm answer from Leica on that). It was only until I moved the database and all temporary and working folders over to the open 4TB drive that it worked properly. I'm not sure if it was situational on the files, the cyclone install, the computer running it. Lots of factors, I intend to do some further testing to see if I can rectify the issue to use the decent horsepower we've put in place to handle these tasks efficiently. Ideally that would be the best route though.