Why is the "ci_sessions" table type MyISAM?

[eluser]waspfactoryuk[/eluser]
My understanding is that the key advantage of InnoDB here is that it has row level locking whereas MyISAM has table level locking. If you are updating a MyISAM table, the table is locked and reads are queued until the write is completed. With InnoDB, a write only locks the affected row so the remaining unaffected rows in the table can still be read.

If the site doesn't have a large number of concurrent users, there probably won't be much difference, but as soon as you have multiple users all trying to read/write the same table, it quickly becomes a bottleneck.

Yes, MyISAM may be quicker and InnoDB may enforce relationships, but these factors are irrelevant here. The issue as I see it is that MyISAM can only be quicker if the table you are trying to read from is not locked therefore InnoDB is a more appropriate choice for concurrent users.

Sorry to drag up an old post but there is not a great deal around on this subject.