Issue Bug Closed

#83451DatabaseRowsUpdateWizard Out of Memory on big tables

Alexander Opitz 01/02/18, 16:15 updated 03/23/20, 14:52

Description

The “database migrations on single rows” wizard selects complete tables, which leads to memory exhausted on large tables (on my system 1,6 million rows) as all rows get selected. Normally the rows should only be read from database while one row is processed after the other one (as we don’t use something like fetchAll) but there are PHP issues around the buffering on MySQLi and pdo_mysql drivers.
See https://secure.php.net/manual/en/mysqlinfo.concepts.buffering.php about this (And special one in MySQLi see https://github.com/doctrine/dbal/blob/master/lib/Doctrine/DBAL/Driver/Mysqli/MysqliStatement.php#L192).

So we should move from select all to select only 1(0).000 rows at once. This will be slower but helps in this OoM issue.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.