[mythtv-users] On the verge of giving up

[Greg Estabrooks]

> One thing that is clearly causing this is the two-page-long SQL
> statements the thing throws to a completely unoptimized, chaotically


 The BFSQ only gets run inrelation to scheduling or rescheduling and is done
by the backend, not the frontend. Not when you move in/out of the recording screen and such. If you are seeing that kind of delay just to navigate the system or start payback of a recording you have something else going on

 And assuming you are not running an ancient version of myth almost all reading from the settings table is also cached by the app so it wont load the same setting from the database several times


 What are you running on?  Using the QT or OpenGL Painter?\