[mythtv] innodb vs myism preformance

[Daniel Manjarres]

Hi guys, Sorry if this isn't exactly core mythtv code related.

I always have been unhappy with the GUI pausing for several seconds
after deleting recordings, so I decided to try converting the database
tables from MYISM to innodb to see if there would be any performance
difference (innodb has row-level locking, so I figured that might
speed things up). The system doesn't pause at all anymore when
deleting (even deleting several recodings back to back), but I forgot
to test delete speed with the 0.17 code before doing the conversion,
so I can't tell if there was a change in the code base that would
speed this up regardless of the database format used.

All tables converted successfully, except for "nestitle" , which
complained thusly:

==
ERROR 1214 at line 1: The used table type doesn't support FULLTEXT indexes
==

I don't think this error is a big deal.

I was wondering if anybody else had tried using innodb tables, and if
it was safe to recomend switching to novice users, and if there had
been a set of changes to 0.17 to speed deleteing up without having to
switch formats.

in case anybody else wanted to try it here's what I did (on debian)


as root, running bash:

cd /var/lib/mysql/mythconverg

for a in $(ls *MYI | cut -f1 -d. ); do echo "use mythconverg; ALTER
TABLE $a TYPE=INNODB;" |mysql ; done


thanks for mythtv!

Dan Manjarres