tables sessions, node_counter and cache and all must be not MYISAM - tebles must be INNODB, otherwise the loaded site will be slow

Comments

damien tournoud’s picture

damien tournoud commented
Title: tables must be not MYISAM - tebles must be INNODB » Recommend InnoDB tables for performance
Category: bug » feature
Priority: Critical » Normal

This is not a bug, reassigning as a feature request.

scoutbaker’s picture

scoutbaker commented
Version: 5.7 » 7.x-dev

And all feature requests go against current dev.

treksler’s picture

treksler commented

just tested
innodb was slower ... a LOT slower for sessions
no difference for other tables

kiev1.org’s picture

kiev1.org commented

myisam lock table in the moment of record in her values - that a base, in not dependence on power of server, can serve in one moment to time only read one node from one user.

sharique’s picture

sharique commented

Innodb provide transaction support, which very important for enterprise cms.
We can also adopt mix of innodb and myisam for performance.
--
Sharique

rantenki’s picture

rantenki commented

Sessions can sometimes be broken by InnoDB usage, depending on configuration. In particular, there is a race condition in the current (6.1) upload module where in some cases the page load for the upload occurs BEFORE the session update completes with a list of uploaded files. When this occurs, the upload fails, sometimes with unusual results. If InnoDB is set, we should have a start transaction / commit wrapper around session updates.

Crell’s picture

Crell commented
Status: Active » Fixed

In another issue, MySQL was already set to default to InnoDB if available.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.