search

K4kArot2015 / sigplus

Automatically exported from code.google.com/p/sigplus
0 stars 0 forks source link

Enhacement. DB engine election #118

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 

I've noticed that with default mysql DB engine of current SIGPlus 1.5+ (InnoDB) 
the performance is many times worse that if we use the MyIsam engine.

I think the InnoDB engine capacity is not needed at all since most frequently 
performed operations are read operations. In this case I think the MyIsan 
engine wins (I can see a substantial performance increase since I changed the 
default engine in my +100 images galleries).

Original issue reported on code.google.com by mper...@gmail.com on 6 Apr 2015 at 7:35

GoogleCodeExporter commented 9 years ago 
There is definitely a performance penalty when using the InnoDB engine. InnoDB 
is used as the preferred engine in order to maintain referential integrity 
between sigplus tables, such as when an image is deleted, all image captions 
and image metadata are cleared from sigplus tables. However, most of the 
database operations in sigplus should incur a penalty on updating and deleting 
rows from database tables, and not on database queries. On the other hand, if 
MyISAM can guarantee referential integrity, I am open to switching to this 
database engine, I do not have a personal preference of one over the other.

Original comment by huny...@gmail.com on 6 Apr 2015 at 6:13