I read something earlier about someone changing all their Rivendell
tables to using the MyISAM engine instead of InnoDB to fix the problem.
So I tried that now. This fixed the long delay for me.
Don't really know how or why, but it solved it. Adding, changing and
removing VT's works in a snap now. Tho, the data on this system is just
setup as a local test, so it's not very important.
Also worth noting is I'm running MySQL bound to 127.0.0.01 and have
skip-networking and skip-external-locking in my.cnf. After converting to
MyISAM, I also defined default-storage-engine to MyISAM in my.cnf.
Is this a safe thing to do, or is this just a quick and potentially
unsafe hack?
Marius
On 02/20/2014 02:07 AM, Pedro Picoto wrote:
The only apparent variable is that the early february DB was free from
consecutive playback during a week.
The issue occurs only on the RDLogedit.
Any operation regarding moving, adding, copy on the RDAirplay runs
quick and flawlessly
Updating an on air log takes while but I consider normal.
Is there a way to purge the DB regarding old logs?
On Thu, Feb 20, 2014 at 12:12 AM, Cowboy <[email protected]
<mailto:[email protected]>> wrote:
On Wednesday 19 February 2014 06:53:44 pm Pedro Picoto wrote:
> Isn't this a DB problem instead of a device
> config one?
Not necessarily.
It would probably be handy to compare various settings
from one database to the other.
--
Cowboy
http://cowboy.cwf1.com
Feel disillusioned? I've got some great new illusions ...
_______________________________________________
Rivendell-dev mailing list
[email protected]
<mailto:[email protected]>
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
