Version: 1.1 (using 4.1.2 (KDE 4.1.2), Kubuntu packages) Compiler: cc OS: Linux (x86_64) release 2.6.27-4-generic Dolphin is too slow when surfing folders, moving one folder to another and other actions. As i can see in process list - when i browsing with dolhpin, some nepomuk process takes all my processor. I don't know exactly what nepomuk is.
@Stefan: I'll try to make some analyzes during the next 2 weeks. It seems when entering directories the first time nepomuk consumes a lot of time for getting the meta information of one file (= the entered directory).
*** This bug has been confirmed by popular vote. ***
I've been doing some tagging and dolphin is really slow. I have some 20 tags and selected 100 files to tag them. nepomukservicestub nepomukstorage is occupying 350MB of memory, maybe we have some leeks
nepomukstorage taking a lot of memory is the often discussed java problem. The service uses a java backend. I am working on a replacement. As for Dolphin speed: I have no problem here. Did you try 4.2 rc already? It should improve the situation a lot.
I have been seeing severe slowdowns in Konqueror on Fedora10/x86_64/KDE 4.2. Opening large directories (4074 files/85 subdirs) would freeze Konqueror for 1-2 min, then freeze again every time I tried to scroll. System load remained low and other apps were responsive. Dolphin acted the same. This behaviour would randomly come and go, and logging out and back would usually fix it. Reported to Fedora as: http://bugs.kde.org/token.cgi?t=NenCcBKgfP&a=cfmpw with partial straces of the hang. Disabling Nepomuk/Strigi fixed the issue. Konqueror is fast and responsive again.
Apologies for the bad link - reported to Fedora as: https://bugzilla.redhat.com/show_bug.cgi?id=487089
Re comment #5, did you install any soprano-backend-sesame2 package from kde-redhat unstable or elsewhere? If you didn't, it's a Redland issue, not a Java issue, we still don't have Sesame2 in Fedora because packaging it according to Fedora's guidelines is months of work (the package in kde-redhat unstable uses the binary JARs and is thus not acceptable in Fedora).
Did you test the sesame2 Soprano backend as suggested?
Apologies for the delay - I missed the initial response. The only soprano rpm on my system is soprano-2.2.3-1.fc10.x86_64. I haven't installed anything from unstable. I've just been leaving nepomuk disabled to work around the issue.
Sure, without the sesame2 backend that is the way to go. So in the end there is not much to do from my end. You simply need Fedora packages for sesame2...