[mythtv-users] BE 2 - Remote Frontends Sluggish on FF

[Stephen Worthington]

On Mon, 6 Nov 2017 09:39:21 -0600, you wrote:

>
>
>Hi Mark!
>
>>> Now the problem is I can't find where the configuration  for two CPU's
>>> (both/all cores) is.  His Section X: Configure MythTV Backend > General
>>>   > |Max simultaneous jobs on this backend: 2|  is set for two.  But
>>> that's jobs and not cores.  (More or less talking to myself to try to
>>> sort things out.)  Find "core" - nope.  Find "cpu" - nope.  "Processor"
>>> - nope.
>> Try maybe mythfrontend - setup - playback - select current video playback profile - select one of the entries (you may have only a single entry) - max CPUs.
>>
>> https://www.mythtv.org/wiki/Configuring_Frontend#Edit_Playback_Profile_Entry
>
>Oh!  I was looking on the Backend's Setup figuring that's where the 
>problem is.
>
>OK - finally found that: in the EDIT sub-page.  Here on the laptop I'm 
>using for testing (Intel dual core) jumped from 1 to 4 at the core 
>option.  Playback didn't like 4 at all.  Manually entered 2 and was 
>happier but everything looked unchanged at playback/FF/Rewind (FF still 
>has a pause before it starts forwarding and still skips, plus rewinds 
>further than it should -- 30 seconds to a minute even though FF at a 
>slow rate.)
>
>And not trying to be contrary but I'm thinking the problem is something 
>in the configuration of BE2's configuration as any Frontend connected to 
>it (BE2) has the problem but the same Frontend configured to connect to 
>BE1 (the old Backend) has an immediate response to FF and advances the 
>frames a heck of a lot quicker, plus doesn't rewind more than about few 
>seconds -- that rewind option is set at the default value on the FE's.
>
>Barry

Each frontend will be creating settings for itself on the new backend
the first time it connects to it.  So its settings on the new backend
will be the defaults plus any changes you have done since then.  In
order to work out whether the frontend settings or the backend are the
problem, it would be useful to copy the settings for a frontend from
the old backend to the new backend.  It is possible to do that as long
as the databases are running the same database schema.  I have not
been following this thread in detail, so I am unsure if both the
backends are running the same MythTV version.  If they are, then the
following procedure should do that.

This command should make a copy of the settings for a frontend on the
old backend:

mysqldump -u mythtv -p --no-create-info mythconverg settings
--where="hostname='savaidh'" >savaidh.sql

It will as you for the MythTV database password - you can find that in
your config.xml file.

Change my hostname "savaidh" to the hostname of your frontend.

On the new backend, make sure you have a backup of the current
database in case you have problems with this procedure.  You will be
altering its database and a typo can cause a disaster.

On the new backend, run:

mysqldump -u mythtv -p --no-create-info mythconverg settings
--where="hostname='savaidh'" >savaidh_backup.sql

This creates a backup file of the existing frontend settings, so you
can restore them if you want to.

Make sure that the frontend you are changing the settings for is not
running mythfrontend for the new backend.  If it is, shut down
mythfrontend.

Copy across the .sql file from your old backend and run this:

mysql -u mythtv -p

It will as for the password of the new backend database, then give you
a prompt waiting for SQL commands.  Give it these commands (replacing
my frontend hostname with yours):

delete * from settings where hostname='savaidh';
source savaidh.sql
quit

Then you can connect that frontend to the new backend and see if
things work differently.

To go back to the previous frontend settings, just do the above again
but change the source line to:

source savaidh_backup.sql

Or you could do a full restore of the database from your backup.