On Feb 15, 2013, at 04:44 19, Alessio Elmi wrote: > The strange thing, as Wayne reported, is that "ripcd" takes a lot of > resources and "caed" too.. It would be nice to know what could be the > reason, using external Apache/MySQL/storage would make any > difference..
It'd be hard to say without knowing the precise setup and then profiling the appropriate code. While indeed ripcd(8) started as a simple message-passing component (hence its name: Rivendell InterProcess Communication Daemon), there has has been quite a bit of other functionality bolted on over the years as Rivendell has developed --e.g. running various system maintenance routines for purging expired cuts, to name just one. As for caed(8), one clear CPU-buster is using MPEG Layer 2 in the library with ALSA or JACK. This will cause a very material increase in CPU utilization, especially when doing captures. Thus, an AudioScience ASI6xxx series card is highly recommended for such setups as that allows all MPEG processing to be offloaded from the main CPU (although obviously not an option for the Raspberry PI). Cheers! |-------------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-------------------------------------------------------------------------| | A rock pile ceases to be a rock pile the moment a single man | | contemplates it, bearing within him the image of a cathedral. | | -- Antoine de Saint-Exupery | |-------------------------------------------------------------------------| _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
