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
This would suggest that each query from Rivendell opens a new TCP connection to
MySQL, which would be bizarre behavior. Is that really how it works? I don't
think MySQL does a reverse DNS lookup for every client query, just for each
connection. And I doubt that's default behavior to do reverse
Hi,
Apologies for the confusion by query I meant the whole loop of creating
a connection, querying and then closing the connection. It was something
I noticed on an old IIS server mainly with php pages where the
connection loop would happen quite a lot as you navigated pages.
The only time
Yeah that would happen with php scripts that run from top to bottom on each web
request. But in something like Rivendell, the MySQL connection (or
connections) ought to stay open for the entire duration that the app is open,
and closed only when the app is exited.
Sent from my iPhone
On May
On May 16, 2013, at 10:17 16, Brian McKelvey wrote:
This would suggest that each query from Rivendell opens a new TCP connection
to MySQL, which would be bizarre behavior. Is that really how it works?
No, it doesn't work that way. It's one connection per module instance, which
is then used
On 05/16/2013 03:51 AM, Wayne Merricks wrote:
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
Why not just install a caching dns server? The distros I've played with
have the dns server set up as a
Right, thanks for the clarification. That's exactly how I would have expected
it to be implemented, and is the right way to do it.
Brian
Sent from my iPhone
On May 16, 2013, at 10:20 AM, Fred Gleason fr...@paravelsystems.com wrote:
On May 16, 2013, at 10:17 16, Brian McKelvey wrote:
This
On Thursday 16 May 2013 03:10:58 pm Kevin Miller wrote:
On 05/16/2013 03:51 AM, Wayne Merricks wrote:
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
Why not just install a caching dns server?
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
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
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
Are you using rdlogmanager to choose songs? I have one system at a station
that doies that, and it takes 25 minutes to generate a log. On another
station that merges a separate music log, generating a log is virtually
instantaneous.
Rob
On Sun, 12 May 2013, Peter Claes wrote:
Guys,
How
RD Log manager can take some time to generate a log if you have a lot of
songs in the library and have a number of rules relating to the selection.
1.5 hours would be in the normal range. We run log generation from a shell
script at 2am each day, when the time it takes bothers no one.
Robert
Yes, we let rdlogmanager choose ..
It's set as a cron job every night, so it doesn't really matter how long it
takes.
But sometimes -if i have changed things- i have to do it manually, and it
takes ages :)
what do you use Powergold ?
The biggest issue that I have is that rdlogmanager uses -last
I use rdlogmanager to create logs from the commandline.
My work station takes about 4 minutes to make each days log but the home
station takes about 40 minutes to make each log. I guess it comes down to
the number of rules and size of the mysql database for the system.
Main differences I see is
Guys,
How long does it take to generate a log on average ?
1.5 hours, would that be normal ?
Regards,
Peter
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
I'm not a specialist, But I think it may largely vary according to your CPU
and specially according to how your clocks, grids and rules are set.
Some time ago I made some changes in artist separation and after it took
very longer to complete.
The more complex, the more time it will take.
17 matches
Mail list logo
