[TYPO3-english] Saving pages in BE locks complete database

Dmitry Dulepov dmitry.dulepov+t3ml at gmail.com
Wed Jan 27 12:48:09 CET 2010


On 2010-01-27 13:43:17 +0200, Christopher Lörken said:
> Ok, I've enabled the slow query log and it just happened again. I've
> extracted the time frame in question and attached the
> "mysqldumpslow -l" (-l == "don't subtract lock time from total time")
> of that part of the log.
> In this case, the longest taking query is definitely this one:
> Count: 1  Time=876.00s (876s)  Lock=0.00s (0s)  Rows=0.0 (0),
> site[site]@localhost
>    UPDATE pages
>    SET
>    WHERE
>    uid=N
> Which, given that I did the magical alter pages to InnoDB, should never
> ever take that long should it? An update of a single primary key
> referenced row in an InnoDB table. And the accessed page is a seldomly
> accessed one so I don't even think that it got accessed during the
> timeframe in question.

Did you do ALTER TABLE for the second time as I suggested? It directly 
affects performance of such queries. If you are interested why you 
should follow my advice, google for "InnoDB fragmentation".

Dmitry Dulepov
"Trust me, I am a doctor!" (c) Gregory House, M.D.

More information about the TYPO3-english mailing list