Byte and Switch<\/a> has an article about how Pixar<\/a> rendered and processed their latest feature film, Cars<\/span><\/a>. <\/p>\n

They talked with Pixar’s VP of technology, Greg Brandeau, to find out more.<\/p>\n

Brandeau says that Cars<\/span><\/a> has put more internal strain on his systems than any other Pixar film to date, ‘…swallowing up a colossal 2,300 CPU<\/span> years over the course of the last five years. In other words, in Brandeau’s view, a single CPU<\/span> would have to run for 2,300 years in order to do all the number crunching for this movie.’<\/span> says the article. <\/p>\n

Here are some more facts about the movie and its processing…<\/p>\n

– it used 300 times more compute power to make than Toy Story
\n – 1 gigabyte of memory wasn’t enough on their server heads. They had to use something in the region of 32 gigabytes.
\n – After to switching to a SAN<\/span>, Pixar cut its rendering times from 10 hours per frame (which should have been normally 1, but the frames created so much stress on the servers, it just didn’t happen), down to 1 hour per frame.<\/p>\n

To find out more about Pixar’s switch to SAN<\/span>, click here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"