I am moving over a thread started on P&T's Get Satisfaction.
I am getting a MySQL timeout saving an entry that had a 10-column Matrix field and some 70 rows. Raising the MySQL limits fixes the immediate problem (we can save), but seems to point at a bigger underlying issue -- entries take a surprisingly long time to save and open, while showing relatively normal benchmarks in EE's debugging panel.
To isolate the problem, I set up a separate, fresh EE install with Matrix as my only plugin. I then created a single channel field with a Matrix of 10 text-only columns.
In this environment, an entry with a single Matrix with 100 rows took 47 seconds to save. However, an entry with 8 Matrix of 13 rows each (104 total rows) took 7 seconds to save. More interesting, the benchmarks for Loading Time, Total Execution Time, and Controller Execution Time were all very reasonable (0.2 to 0.4 or so).
I would like to keep these entries in a single Matrix table, if possible. Is this just an effect of saving a table with this many cells (and a natural limit of EE, Matrix, or MySQL). Or is there's something else at play?