performance

With folks using Media Mover to transcode larger and larger video files, cron time outs have become somewhat of a problem as Drupal waits for FFmpeg to complete its processing. With Media Mover one, configurations are run from cron by default (not required, but out of the box) which means that cron runs as long as the Media Mover configuration takes. While it is possible to limit cron runs, the reality of transcoding a gigabyte file is that it takes time regardless of how much horsepower you can throw at it. Media Mover one was setup to be friendly to multi-machine systems, but the system left some things to be desired.

If you're interested in doing code profiling, KCachegrind is a great utility to investigate what part of your code is hogging CPU time. If you're on a debian or ubuntu machine, it is simple to install. If you're on OSX... well you've got a bit of work to do.

When I first was building Media Mover, I put in a number of options that allowed an administrator to control how and when various configurations were run. For example, while Media Mover runs on cron by default, one could prevent this and use alternate means to run configurations. settings.php can also turn off specific configurations- very useful in a multi server environment where you want one box to serve the web content and different one to do the transcoding of files.
 

Media Mover can be pretty CPU intensive- transcoding with FFmpeg can be a substantial hit on your server resources. If you couple this with a large amount of batch processing, you are looking at high loads over a long period of time.