Latency can be an issue with MySQL but only usually if you don't have good DNS on your network. To test this out you can just disable the DNS checking in the mysql config file. Just add skip-name-resolve under [mysqld] in my.cnf. You can normally see this is at fault if it takes forever to log into MySQL from a remote machine (several seconds delay before anything even happens). This delay happens every time the remote machine sends a query so even if MySQL completes the query in 100ms you'll have that 3+ second delay tacked on top.
The main reason for the time difference for us is the Riv virtual machine is running on an old Core 2 Duo restricted to just 1 core in the VM. The server is a modern quad core xeon (approx 6months old now) so our time difference is purely down to more available processing power. Regards, Wayne On 15/05/13 17:55, Brian McKelvey wrote: > Maybe there are tons of MySQL queries happening during the process, and the > latency savings from being on the same machine as MySQL so the queries don't > have to go over the network really adds up? > > Brian > > Sent from my iPhone > > On May 15, 2013, at 6:04 AM, Wayne Merricks <[email protected]> > wrote: > >> In theory yes, I generate my logs on a server that houses the MySQL >> database and NFS shares. It doesn't do any playout and is CPU idle most >> of the time. >> >> We don't have any particularly complicated rules but we do have about >> 10,000 carts. Standard generation time is about 2minutes on a random >> workstation with a Rivendell virtual machine and fairly instant >> (measured in seconds) on the server. >> >> Regards, >> >> Wayne >> >> On 15/05/13 13:46, Alan Peterson wrote: >>> Does it make a difference if the log is being generated on the same machine >>> handling the playout? I would think with that much brainpower being devoted >>> to uninterrupted play, log generation happens in those little moments when >>> RDAirplay is catching its breath. >>> >>> Would it be any faster if a log is generated on a dedicated off-air machine? >>> >>> -a. >>> _______________________________________________ >>> Rivendell-dev mailing list >>> [email protected] >>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
