[mythtv-users] Slow MySQL query after delete

[Michael T. Dean]

On 11/30/2007 03:55 AM, David Rees wrote:
> On Nov 29, 2007 6:38 PM, Michael T. Dean <mtdean at thirdcontact.com> wrote:
>   
>> I have 2 dedicated backends.  Each has a disk with a 16GB partition for
>> the system.  The rest of the disk with the system partition is not used
>> for (active) recording, but only for archived storage of recordings.
>> It's all just a matter of configuration.  I used to have a system with a
>> 16GB HDD for my system partition with all recordings on other disks.
>>     
>
> So does each of your backends have 2 disks? No? Just separate
> partitions? Tsk tsk...
>   

I have 3 disks in each backend.  2 disks used for active recording.  One
disk has the system partition and a partition used only for archival.

>> In other words, my system seems--to me--to be proof that a system that
>> takes 6-7 seconds to execute the scheduling run does not lock up when a
>> recording is deleted.  Perhaps I'm just naive, though, in thinking my
>> system acts like a properly configured Myth system.  Maybe I've
>> misconfigured my system and gotten unreasonably good performance because
>> of it.
> I suspect your mythconverg database is using InnoDB instead of MyISAM.
>   

Nope.

Mike