They're serviced by multiple nodes and have very strong backup policies.
At rhythm and Hues, you could request footage all the way back from the founding of the studio for example.
CG work is fairly IO intensive for tasks like rendering where you're reading hundreds or even thousands of geometry caches per frame. But for other things, your IO isn't as frequent since it's not about constant r/w as there are long computational or artist time between saves and reads.
At rhythm and Hues, you could request footage all the way back from the founding of the studio for example.
CG work is fairly IO intensive for tasks like rendering where you're reading hundreds or even thousands of geometry caches per frame. But for other things, your IO isn't as frequent since it's not about constant r/w as there are long computational or artist time between saves and reads.