Jørn Wildt

It is way tooooo slow at the moment and takes up a whole lot of my CPU processing power and causes MySQL to get very slow in answering queries. I am even thinking about disabling the module at the moment as it gets in the way of normal function.

I see 'LOCK/UNLOCK' tables passing by which is completely unnecessary. Imagedata is collected when not used.

This is a major issue for right now so I am going to look at it first before I am going to do the rest.

Interesting. Let me know what you find out. I'm not that good at databases so "enlighten me" if you find anything.

This "Lock/Unlock" stuff - where do you see it? Perhaps I could take a look at it myself.

Is it possible to do some kind of performance tracking in MySQL?

I found the 'problem'. (though not the lock/unlock statements)

We need to add more indexes to the data structures. My galleries are getting bigger all the time and as there are more columns included in the WHERE clauses than there are indexes we need to add these.

(Some queries took 1.5s to complete and were executed for every thumbnail)
Still i find this too long for such a small table and will have a look at it later.

you could start mysql with --log-slow

but that does not always help. Running the query in the console and see how long it takes to complete does help