[Toolserver-l] transaction isolation level set to READ UNCOMMITTED
Andre Karwath
aka at aka-online.de
Tue Jul 18 20:07:58 UTC 2006
Hi,
>By holding a lock. I don't know if this is the case here, but it would
>be an explanation. Are you using explicit transactions?
No.
> > But I will not start it again - then there are just
> > no statistic updates anymore.
>
>Please tell me what queries exactly the script performs. I'm pretty sure
>this could be done more efficiently somehow - for example, by using at
>the recentchanges table instead of revisions.
No, the recentchances does not help. For the statements, please
see "~aka/Cronjobs/UpdateDEUserStat.pl". The long running function
is called "GetUserCounts". Its pretty straight forward.
I already played with caches and so on, but this introduces other
problems. So, I have no idea how I can still further improve the
script without loosing functionality.
If you have an idea, please drop me a (private) mail, and you can
write in German then ;)
Regards,
Aka
More information about the Toolserver-l
mailing list