In my experience, it certainly wasn't a network thing, nor was it waiting for a request to time out. The hard drive activity light was solid, and mysqld and/or some kernel disk process would be consuming all available cycles.
I do not know exactly why, but adding the noatime significantly sped things up. It still takes a second or so, but it's orders of magnitude better than it was. On Wed, Feb 19, 2014 at 4:53 PM, Brian McKelvey <theturtl...@gmail.com>wrote: > I have a hard time believing this has anything to do with the file system > mount configuration on a stock Linux distro. For NFS, sure. But for > local? Not likely. Almost certainly something else is up. > > I might be inclined to start investigating network related things. DNS, > the "hosts" file (making sure the machine's local hostname maps to > 127.0.0.1), etc., even if the machine isn't connected to a network. > > I suspect there's some kind of request timeout somewhere. > > Brian > > Sent from my iPhone > > > On Feb 19, 2014, at 4:12 PM, Cowboy <c...@cwf1.com> 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 > > Rivendell-dev@lists.rivendellaudio.org > > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
