I've run some of the test materials on my own machine (Macbook Pro Retina, 13-inch, Late 2013, 2.4GHz Intel Core i5).

Big Buck Bunny trailer took 5m04s (2.71fps).

Carl, I've emailed you the log file etc so it can be added to the benchmarks.

Would be very interested to hear how the Raspberry Pi compares! And Carsten, do you think I should be getting better performance? It's running 4 threads (processor has 2 cores hyper-threaded) & DCP-o-matic is pretty much maxing out the CPU.

Jim


On 28/04/2015 17:40, David Nedrow wrote:
I’ll do new tests with Carl’s “official” test materials, that way people can get a direct comparison with there own setup.

-David


On Apr 28, 2015, at 11:19 AM, Jim Dummett <j@dummett.org> wrote:

Even more interesting! Please keep us updated as you add more nodes.

When you say 1 frame per sec, what format are you encoding from/to? I've found on a Macbook Pro retina with 2.4Ghz i5 processor, encoding from 1080p ProRes Quicktime to Flat container 2K DCP at 100Mbit, I'm only getting 2 or 3 frames/sec. So adding another frame/sec for the cost of a Rasberry Pi would be very good value!

Jim


On 28/04/2015 15:43, David Nedrow wrote:

An inexpensive render farm is exactly why I got DCP-o-matic compiled on the Pi 2.

So far, adding a single Raspberry Pi 2 increased my encode speed by an additional frame per second. I’m working on adding a second Pi 2, so we’ll see if the performance increase is linear.

I’m sure I haven’t optimized the compiled code very well, so with some work we could probably squeeze more performance out of DCP-o-matic.

One benefit I see to using the Pi is that I can easily expand the “farm” one unit at a time as I can afford it, rather than having to shell out for a single big box. Plus, if one goes bad, I can easily replace it. If a single big server goes down, my whole render server is gone.

-David


On Apr 28, 2015, at 4:54 AM, Jim Dummett via DCPomatic <dcpomatic@carlh.net> wrote:

Hi David.

This is really interesting. What kind of performance are you getting from it?

I have been wondering about if it might be a viable option to make a kind of render farm out of 20-50 Raspberry Pi, and whether that'd work out cheaper in terms of processing power per buck than buying one big fast multi-processor machine.

Jim


On 27/04/2015 22:36, David Nedrow via DCPomatic wrote:

I’ve been able to compile DCP-o-matic on Raspberry Pi 2’s using the Raspian disk image. I had to install a few packages and compile/install a couple of third party libraries. I also had to make some changes to the script file to take into account that the CPU is an ARM chip, and not Intel x86.

Carl, any chance you’d be willing to take on another platform for your package distribution? Raspian is a direct Debian implementation, so you should be able to re-use a lot of your setup.

I’d be willing to donate a configured Pi 2 to the project if that would help.

-David



_______________________________________________
DCPomatic mailing list
DCPomatic@carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic


_______________________________________________
DCPomatic mailing list
DCPomatic@carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic