[mythtv-users] No luck with RP3 mythtv inatall

[Peter Bennett (cats22)]

On 05/27/2016 11:43 AM, Tyler T wrote:
>> Raspberry Pi as a master backed in likely to be too underpowered.
> It depends on how "big" of a backend you need. For years I ran a
> master backend on a SheevaPlug, which was a single-core 1.2GHz 512MB
> ARM device -- by all accounts less powerful than an RPi2. For a
> single-tuner HDHR with an OTA antenna and a single remote frontend, it
> worked a treat. I did not do commflagging or transcoding, of course.
>
> My BE now is a Cubox-i4, which is the approximate equivalent of an
> Rpi2 save it has 2GB RAM, eSATA, and gigabit Ethernet. It handles a
> dual-tuner HDHR (OTA) and one remote frontend without breaking a
> sweat. Again, I do not commflag or transcode, but I should think that
> an Rpi2 should be able to do those tasks on spare core as long as you
> weren't scheduling a ton of recordings (so it doesn't eternally fall
> behind on background tasks).
>
> Obviously, if you have a zillion cable/satellite channels and/or a
> stack of tuners, then an RPi may not be the best choice (unless maybe
> you deploy multiple Pis to share the workload ;) ).
>

I don't know what those devices have for a hard drive and a network
interface.

As far as RPI is concerned  - would you want to use the SD card for your
video storage? If you invest in a large SD card it will likely cost more
than the RPI. Would the SD card be fast enough or large enough?

You can attach a USB hard drive. Now you have the hard drive and network
all going through the single 480 mb/s USB pipe. This has to be shared
between frontend, tuner, and all disk I/O. Will this work?

The other problem I see is the 1 GB memory. Is this enough to run mysql
and the backend?

Maybe it will work. I had thought of trying it but I did not get around
to it yet.

Peter