Page 1 of 1
inoodb should be used only in this following case
Posted:
Tue Mar 03, 2009 5:56 pmby bobbymc
my vicidial_log table has gotten so big that it started to lock up.. i understand it should be archived and processed into a detailed table and etc.. but if that's not a option i found innodb for that specific table ONLY to be a perfect solutions.. So i recommend if you got over 10 million records in that table.. change it to innodb
Posted:
Sun Dec 12, 2010 4:38 pmby williamconley
newer versions allow pushing to a report server, on which innodb would certainly be a good idea for a table this large.
Posted:
Mon Dec 13, 2010 10:28 amby mflorell
You could still have problems with InnoDB and that table. Any reason you are not using the archive script?
Re: inoodb should be used only in this following case
Posted:
Mon Jul 16, 2012 4:56 pmby bobbymc
stuck on a old version 2.0.5rc5 =(
Re: inoodb should be used only in this following case
Posted:
Mon Aug 13, 2012 7:55 amby mcargile
InnoDB does not do table level locking. It does row level locking. This is why it performs so well. However Vicidial REQUIRES table level locking. Without it you will have concurrency problems. You are probably having them right now and just not noticing it. I recommend downloading a copy of the archive script and see what it is doing, and then manually perform those actions on your load tables.