I have no idea if the 29 hour figure is accurate. However, regardless of how long it takes, I would assume that frames are rendered in parallel.

The original Coco frame times were 1000hrs/f, thanks to millions of light sources (and coming in at 30GB to 120GB of scene data). But engineers got that down to 50hrs/f over the course of production - light acceleration structures that have now ended up in RenderMan 22. (These numbers are single core benchmarks, so you then need to scale by some factor of numbers of cores you have available). In general, I think it’s the huge scene data size that keeps feature films mostly on the CPU.

https://www.fxguide.com/featured/rendermans-visuals-for-coco...

Being why nvidia are selling GPU's with 48GB of ram...

It takes 29 hours for a single CPU core (or thread?) to render one frame, which is reasonable for Pixar-quality scenes.

Big Hero 6 was rendered using 55,000 CPU cores in parallel, which would bring the final render time closer to 70 hours for 144k frames (assuming maximum efficiency and ignoring all the tests and overhead).

For reference you can download a production benchmark scene (https://www.blender.org/download/demo-files/) from the Blender team's short film and try to render it at 1080p — my 16-thread Ryzen CPU takes over an hour to finish one frame.

Also feature films are rendered in 4K or above which quadruples the render time over 1080p.

Parallelism is a thing.

29 hours wallclock is long for a render but not uncommon.