Archive is painfully slow

Flame Flame Questions
1

My archive is painfully slow. It took me half an hour last night and I am sitting here again thinking maybe this isn’t normal. Maybe someone knows something that I don’t.

My archive is going to verify the archived media for me and I wonder if this is what is slowing things down.

If I look at my shell I get a lot of this:

I/O on unreferenced frame 0xbc006de27000015a
Could not open '/opt/Autodesk/cache/slates/110300/0xbc006de270000160.456x256.ef4f67f545fe53e48b79115f369b6efd' for writing : No such file or directory
Could not set '0xbc006de270000160' in cache: Could not open '/opt/Autodesk/cache/slates/110300/0xbc006de270000160.456x256.ef4f67f545fe53e48b79115f369b6efd' for writing : No such file or directory
Could not open '/opt/Autodesk/cache/slates/110300/0xbc006de27000015d.456x256.ef4f67f545fe53e48b79115f369b6efd' for writing : No such file or directory
Could not set '0xbc006de27000015d' in cache: Could not open '/opt/Autodesk/cache/slates/110300/0xbc006de27000015d.456x256.ef4f67f545fe53e48b79115f369b6efd' for writing : No such file or directory
/usr/bin/stat: cannot stat ‘*.otoc’: No such file or directory
Done
/usr/bin/stat: cannot stat ‘*.otoc’: No such file or directory
Done
Could not open '/opt/Autodesk/cache/slates/110300/0xbc006de2700001a1.456x256.ef4f67f545fe53e48b79115f369b6efd' for writing : No such file or directory
Could not set '0xbc006de2700001a1' in cache: Could not open '/opt/Autodesk/cache/slates/110300/0xbc006de2700001a1.456x256.ef4f67f545fe53e48b79115f369b6efd' for writing : No such file or directory
Could not open '/opt/Autodesk/cache/slates/110300/0xbc006de2700001a4.456x256.ef4f67f545fe53e48b79115f369b6efd' for writing : No such file or directory
Could not set '0xbc006de2700001a4' in cache: Could not open '/opt/Autodesk/cache/slates/110300/0xbc006de2700001a4.456x256.ef4f67f545fe53e48b79115f369b6efd' for writing : No such file or directory
Could not open '/opt/Autodesk/cache/slates/110300/0xbc006de2700193a1.456x256.ef4f67f545fe53e48b79115f369b6efd' for writing : No such file or directory
Could not set '0xbc006de2700193a1' in cache: Could not open '/opt/Autodesk/cache/slates/110300/0xbc006de2700193a1.456x256.ef4f67f545fe53e48b79115f369b6efd' for writing : No such file or directory
Could not open '/opt/Autodesk/cache/slates/110300/0xbc006de27005e6a1.456x256.ef4f67f545fe53e48b79115f369b6efd' for writing : No such file or directory
Could not set '0xbc006de27005e6a1' in cache: Could not open '/opt/Autodesk/cache/slates/110300/0xbc006de27005e6a1.456x256.ef4f67f545fe53e48b79115f369b6efd' for writing : No such file or directory
Could not open '/opt/Autodesk/cache/slates/110300/0xbc006dce70004302.62x35.4ce17c0e15e88e36e03729e49f7cf46c' for writing : No such file or directory
Could not open '/opt/Autodesk/cache/slates/110300/0xbc006de27005e6fd.456x256.ef4f67f545fe53e48b79115f369b6efd' for writing : No such file or directory
Could not set '0xbc006de27005e6fd' in cache: Could not open '/opt/Autodesk/cache/slates/110300/0xbc006de27005e6fd.456x256.ef4f67f545fe53e48b79115f369b6efd' for writing : No such file or directory
Could not open '/opt/Autodesk/cache/slates/110300/0xbc006de370000100.456x256.ef4f67f545fe53e48b79115f369b6efd' for writing : No such file or directory
Could not set '0xbc006de370000100' in cache: Could not open '/opt/Autodesk/cache/slates/110300/0xbc006de370000100.456x256.ef4f67f545fe53e48b79115f369b6efd' for writing : No such file or directory
/usr/bin/stat: cannot stat ‘*.otoc’: No such file or directory
Done
PID 18495: Cannot set lock "/Volumes/beast/BJ1604_Sky_Goodoil/archive/BJ1604_Sky_Goodoil_hoummus/BJ1604_Sky_Goodoil_hoummus-lock" - Operation not supported
Could not read lock file: Could not read /Volumes/beast/BJ1604_Sky_Goodoil/archive/BJ1604_Sky_Goodoil_hoummus/BJ1604_Sky_Goodoil_hoummus-lock: No such file or directory

20 mins into the process now and I am looking for any suggestions.

Thanks

2

We get a lot of this. I believe it might have something to do with verification and or otocs. Haven’t got to the bottom of it. It makes opening and closing archives slow. I would like to get to the bottom of it.

1 Like
3

The best way is to contact the support team so they can investigate the issue. At first sight, it seems wrong that a lock cannot be created. You may use a filesystem that doens’t support the required Unix semantic.

4

I know this won’t fix your problem now… but I’m curious why more people don’t archive without media/cache. It’s a huge waste of space as long as flame converts everything to uncompressed media.

I’ve been making archives with no media/no cache for 8 years. Put the archive with original media to tape or whatever, restore all when needed. Flame archives are Megabytes at the most.

The dream would be an archive option to package all source material (like other modern software that uses many media files).

Relevant Improvement Request:
FI-01367

5

Or at the very least use OpenEXR PIZ instead of RAW.

2 Likes
6

Thanks @fredwarren
Useful info. I will log a support case and ask our IT about the server.

7

Yeah. We archive without cache media. No renders or cache and it is still slow. Hence my concern. If it was saving 100s of gigabytes then maybe 30 mins would be reasonable. Maybe. But this archive comes out at less than 100mb so it really should take this long.

I’ll look into it and report back.

Thanks

8

I do a lot of long form work, my archives are always just a link (no media/no cache) and usually take awhile. What i would like to see is some kind of system status during the front end of the archive process. I just archived a rather heavy project and it took every bit of 30 to 40 minutes to complete. However, that first 15 to 20 minutes of the process is a beachball…and at that point you start to question if the system is hung…but if you keep the faith, eventually a status screen appears and all is good…but for piece of mind, would love to see something other then the beachball.

2 Likes