Bug#479068: Scanning collection does not finish using SQLite

2008-05-18 Thread Alexander Kurtz
Hi,

Sorry, I was on vacation the last week. Here are your answers. Thanks a
lot for fixing this bug!

Alexander Kurtz

Modestas Vainius wrote:
 1.4.9.1-2 is hitting unstable as I'm writing this mail. Well, I sort of
 reproduced the bug and I hope that I fixed it. Please retest and
 confirm if
 the bug is fixed for you.
100% confirmed, the bug is fixed. The combination of amarok=1.4.9.1-2
and libsqlite3-0=3.5.8-4 (which is even in testing now) scanned my
collection (26000 songs) in less than 20 minutes.
 I also expect that collection building should be
 faster now than it was before.
It is, definitely (1.5 - 2 times faster).
 Also, if you can, please test 1.4.9.1-2 with other engines (MySQL and
 PostgreSQL).
MySQL: Same or slightly faster results compared to SQLite
PostgreSQL: N/A




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#479068: Scanning collection does not finish using SQLite

2008-05-10 Thread Modestas Vainius
Hi,

1.4.9.1-2 is hitting unstable as I'm writing this mail. Well, I sort of 
reproduced the bug and I hope that I fixed it. Please retest and confirm if 
the bug is fixed for you. I also expect that collection building should be 
faster now than it was before.

Also, if you can, please test 1.4.9.1-2 with other engines (MySQL and 
PostgreSQL).

2008 m. May 8 d., Thursday, Alexander Kurtz rašė:
 libsqlite3-0_3.2.1-1_i386.deb: works
 libsqlite3-0_3.3.8-1.1_i386.deb: works
 libsqlite3-0_3.4.2-2_i386.deb: works (38 minutes for 100% of 25000
 songs, CPU load 40-50%)
 libsqlite3-0_3.5.6-1_i386.deb: doesn't work (1 hour for 22%, CPU load
 100%) libsqlite3-0_3.5.6-2_i386.deb: doesn't work
 libsqlite3-0_3.5.6-3_i386.deb: doesn't work
 libsqlite3-0_3.5.7-2_i386.deb: doesn't work (4 hours for 37%, CPU load
 100%)
 libsqlite3-0_3.5.8-1_i386.deb: doesn't work
Alexander, could you do this benchmark with amarok 1.4.9.1-2?

-- 
Modestas Vainius [EMAIL PROTECTED]


signature.asc
Description: This is a digitally signed message part.


Bug#479068: Scanning collection does not finish using SQLite

2008-05-10 Thread Modestas Vainius
Hi,

2008 m. May 10 d., Saturday, robert jacobs rašė:
 Just tried upgrading sqlite to 3.5.8-4. It still appears to go into an
 infinite loop.
The problem is that I don't have large enough collection to reproduce this 
bug. I'll see what I can do.

-- 
Modestas Vainius [EMAIL PROTECTED]


signature.asc
Description: This is a digitally signed message part.


Bug#479068: Scanning collection does not finish using SQLite

2008-05-09 Thread robert jacobs

 @Robert Jacobs: How big is your collection? How long did it take to
 completely rescan it?

55k songs. I've been avoiding rebuilding my archive as long as
possible, because I lose track after 10 minutes. (Admittedly, only a 1
GHz machine, but with fast hard drives. The last time I tried, months
ago, it was at least an hour.)

I was specifically observing that with 3.5.8 even only refreshing
seemed to get stuck in an infinite loop in SQLite. (strace showed one
thread seeking and reading from ~16MB to ~33MB in the sqlite3
database, over and over, never getting anywhere. This is probably
related to (and fixed by?) #480007.

 - robert jacobs



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#479068: Scanning collection does not finish using SQLite

2008-05-09 Thread robert jacobs

Just tried upgrading sqlite to 3.5.8-4. It still appears to go into an infinite 
loop.

 - robert jacobs



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#479068: Scanning collection does not finish using SQLite

2008-05-08 Thread Alexander Kurtz
Hi,

using snapshot.debian.net I did some tests. These are _my_ resultes;
they may need further confirmation!

libsqlite3-0_3.2.1-1_i386.deb: works
libsqlite3-0_3.3.8-1.1_i386.deb: works
libsqlite3-0_3.4.2-2_i386.deb: works (38 minutes for 100% of 25000
songs, CPU load 40-50%)
libsqlite3-0_3.5.6-1_i386.deb: doesn't work (1 hour for 22%, CPU load 100%)
libsqlite3-0_3.5.6-2_i386.deb: doesn't work
libsqlite3-0_3.5.6-3_i386.deb: doesn't work
libsqlite3-0_3.5.7-2_i386.deb: doesn't work (4 hours for 37%, CPU load
100%)
libsqlite3-0_3.5.8-1_i386.deb: doesn't work

I know that libsqlite3-0 3.5.x entered unstable earlier than 2008-03-20,
but I _guess_ that I noticed this bug just that day, because this was
the first time to completely rescan my collection; until that day I had
just refreshed it, so don't take this specific date too serious!

I _suggest_:
reassign 479068 libsqlite3-0 3.5.6-1 and
severity 479068  serious
since rookies will simply chuck away Amarok after waiting for hours for
their collection to be scanned.

@Robert Jacobs: How big is your collection? How long did it take to
completely rescan it?

Alexander Kurtz



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#479068: Scanning collection does not finish using SQLite

2008-05-02 Thread Alexander Kurtz
I can absolutely confirm this behaviour here with amarok 1.4.9.1-1
(Debian testing)

I've already noticed this bug in unstable, after an upgrade around
2008-03-20 (+- 15 days), but I thought that this was normal (my
collection is  25000 songs). Unfortunately I cannot test amarok 1.4.8-1
or 1.4.8-2, since these versions are no longer in the repository and I
got no local copies, however I am almost sure, that this bug doesn't
exist in the current stable version 1.4.4, since I use amarok for a
quite long time now and did not experience anything similar.

I noticed that the speed of amarok scanning the collection is not
constantly slow, but decreasing:
It starts at a normal level (around 10 minutes for 25% of 25000 songs)
but gets slower and slower (I tried to scan my collection for  24 h).

Can I help with any further information, e.g. a translation of  the
forum thread mentioned above?
http://www.debianforum.de/forum/viewtopic.php?f=25t=98916%5D




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]