>
> Hmm, nothing interesting here, the slowest query is 0.2s if I understand it
> correctly, to 20-30 s delays. You say the Amarok event loop stops for that
> extended periods of time. Could you please:
>
> 1. Install debugging symbols for Amarok, kdelibs, qt, glibc, glib
> 2. Run Amarok grom gdb:
On 5. 6. 2012 Alan Ezust wrote:
> Hi Matěj,
>
> Here are the rowcounts for the tables, bad and good
>
> amarok2 amarok3
> (bad) (good)
> albums24852629
> artists 23012335
> composers 199 199
> devices
Hi Matěj,
Here are the rowcounts for the tables, bad and good
amarok2 amarok3
(bad) (good)
albums 24852629
artists 23012335
composers 199 199
devices 12 0
genres 194 195
labels 0
On 4. 6. 2012 Alan Ezust wrote:
> At first, I thought my problem was related to how many tracks I had in
> my playlist (6000) or
> database (13000). Now i realize it is probably more related to how
> many tracks I renamed over
> the years.
>
> I still have the "bad" database if anyone wants me to
