| Summary: | Slow rescan after album added to collection. | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Emanuele Cisotti <e.cisotti> |
| Component: | Collections/Local | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | mitchell |
| Priority: | NOR | ||
| Version: | 2.1.80 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Emanuele Cisotti
2009-09-15 20:54:06 UTC
Are you doing a full rescan on purpose? Why not just do an "update collection"? Sorry I don't speak english good enough ;) I mean that Amarok trying to add the new album takes about 2 hours! I do (and click) nothing on my purpose. What happens if you disable "Watch folders for changes" in the settings, and then add the album and manually choose "update collection"? If it's still slow, post the relevant output of 'amarok --debug' If you are adding the album to the root of your collection, then it will cause the entire collection to be rescanned. Proper organization of files is a good thing... @Mikko: no, it doesn't work, I will try tomorrow to debug. @Jeff: my collection is made by 2 folder, and I putted it into one of this folder. So am I putting in in the root for the collection? I don't know, because I don't know the layout of your folder structure. But just remember, scanning is based on folder mtimes. The flatter your folder structure, the more will have to be rescanned when changes occur. This is the first output when Amarok starts scanning again all my collection: amarok: BEGIN: void ScanManager::startIncrementalScan() amarok: BEGIN: QStringList ScanManager::getDirsToScan() amarok: END__: QStringList ScanManager::getDirsToScan() - Took 2s amarok: GOING TO SCAN: amarok: "/home/ciso/Musica/Albums/" amarok: BEGIN: XmlParseJob::XmlParseJob(ScanManager*, SqlCollection*) amarok: BEGIN: void ProgressBar::setDescription(const QString&) amarok: END__: void ProgressBar::setDescription(const QString&) - Took 4.9e-05s amarok: BEGIN: void CompoundProgressBar::addProgressBar(ProgressBar*, QObject*) amarok: BEGIN: void ProgressBar::setDescription(const QString&) amarok: END__: void ProgressBar::setDescription(const QString&) - Took 3.9e-05s amarok: END__: void CompoundProgressBar::addProgressBar(ProgressBar*, QObject*) - Took 0.00037s amarok: BEGIN: ProgressBar* ProgressBar::setAbortSlot(QObject*, const char*) amarok: Setting abort slot for "Scansione musica" amarok: connecting to 1abort() amarok: END__: ProgressBar* ProgressBar::setAbortSlot(QObject*, const char*) - Took 7.4e-05s amarok: END__: XmlParseJob::XmlParseJob(ScanManager*, SqlCollection*) - Took 0.0011s amarok: BEGIN: SqlCollectionDBusHandler::SqlCollectionDBusHandler(SqlCollection*) amarok: Register object: true amarok: BEGIN: virtual void XmlParseJob::run() amarok: END__: SqlCollectionDBusHandler::SqlCollectionDBusHandler(SqlCollection*) - Took 0.00019s amarok: BEGIN: ScanResultProcessor::ScanResultProcessor(SqlCollection*) amarok: END__: ScanResultProcessor::ScanResultProcessor(SqlCollection*) - Took 9.6e-05s amarok: END__: void ScanManager::startIncrementalScan() - Took 2s amarok: BEGIN: void DatabaseUpdater::createTemporaryTables() amarok: END__: void DatabaseUpdater::createTemporaryTables() - Took 0.0073s amarok: BEGIN: void DatabaseUpdater::prepareTemporaryTables() amarok: END__: void DatabaseUpdater::prepareTemporaryTables() - Took 11s I'm not sure why you gave us that information. Mirko asked for the output of amarok --debug. I don't think that the cause is how much "flat" is my collection because in Amarok 1.4 was working great. I also tried to put a new album inside the folder of another album (so not in the "main" directory) and amarok takes 2 hours for rescanning. |