In KDE 4.10.x, my collection of movies, pictures, music, documents was indexed in few minutes. But now, in KDE 4.10.95, the same collection is being indexed in half hour and has completed ~10% only. Why has it happened?

when you say "few minutes" you mean after the the collection was initially indexed and then a few minutes going forward?

could it be your collection is being migrated http://vhanda.in/blog/2013/04/the-nepomuk-migration/

google01103 wrote:when you say "few minutes" you mean after the the collection was initially indexed and then a few minutes going forward?

I mean indexing was fully completed in few minutes.

google01103 wrote:could it be your collection is being migrated http://vhanda.in/blog/2013/04/the-nepomuk-migration/

No, it couldn't, cause I had deleted the Nepomuk storage (~/.kde4/share/apps/nepomuk/*) before I turned on the indexing.

Another alternative is that Nepomuk is now scanning file types it previously was not able to handle - KDE 4.11 included a new metadata indexer, so chances are this can handle more filetypes than your previous setup.

Does the Nepomuk Controller indicate which file(s) it is taking the time to index?
You might also want to ensure it is not indexing locations you do not want it to index.

bcooksley wrote:Another alternative is that Nepomuk is now scanning file types it previously was not able to handle - KDE 4.11 included a new metadata indexer, so chances are this can handle more filetypes than your previous setup.

It's really sad

bcooksley wrote:Does the Nepomuk Controller indicate which file(s) it is taking the time to index?

No, it doesn't. (Why it doesn't, by the way?)

Hm, it should always indicate the file it is currently indexing at the very least. If it does not show itself as indexing a file, it may be busy doing something else instead (such as indexing your email stored in KMail, which is handled seperately).

Are there any particular processes which are using the CPU aggressively?