[opensuse] kde4: 1.6G nepomuk/ (any way to limit this?)
Guys Wondering why my .kde4 directory had ballooned to 2.7G, I did a du -hs on share/apps and noticed that nepomuk was eating 1.6G of space. I never use this thing and to my understanding it is still an application looking for a use. Yes, it is supposedly some generic metadata handler/index thing. So far I've never found a use for it. However, I'm concerned that it is one of those things that is integrated into everything like windows explorer and I don't know if I can just turn it off without further destabilizing kde4. If I can turn it off, how do you do it? If I can't, then how can I tell it to only use 50M or so? 1.6G is just nuts. I suspect many of you have much larger indexes. Has anyone looked to tone this thing down and keep the index size smaller? All ideas are welcome. (even the -- it's just like beagle -- kill it) approach would be fine. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 15 Dec 2010 14:29:17 David C. Rankin wrote:
Guys
Wondering why my .kde4 directory had ballooned to 2.7G, I did a du -hs on share/apps and noticed that nepomuk was eating 1.6G of space. I never use this thing and to my understanding it is still an application looking for a use. Yes, it is supposedly some generic metadata handler/index thing. So far I've never found a use for it. However, I'm concerned that it is one of those things that is integrated into everything like windows explorer and I don't know if I can just turn it off without further destabilizing kde4.
If I can turn it off, how do you do it? If I can't, then how can I tell it to only use 50M or so? 1.6G is just nuts. I suspect many of you have much larger indexes. Has anyone looked to tone this thing down and keep the index size smaller?
All ideas are welcome. (even the -- it's just like beagle -- kill it) approach would be fine.
David, Personal Settings (Configure Desktop) -> Desktop Search Uncheck "Enable Nepomuk Semantic Desktop" and "Enable Strigi Desktop File Indexer" Then you should be able to remove the 1.6G of nepomuk data and recover the disk space. -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Dec 15, 2010 at 04:59, David C. Rankin wrote:
Guys
Wondering why my .kde4 directory had ballooned to 2.7G, I did a du -hs on share/apps and noticed that nepomuk was eating 1.6G of space. I never use this thing and to my understanding it is still an application looking for a use. Yes, it is supposedly some generic metadata handler/index thing. So far I've never found a use for it. However, I'm concerned that it is one of those things that is integrated into everything like windows explorer and I don't know if I can just turn it off without further destabilizing kde4.
If I can turn it off, how do you do it? If I can't, then how can I tell it to only use 50M or so? 1.6G is just nuts. I suspect many of you have much larger indexes. Has anyone looked to tone this thing down and keep the index size smaller?
All ideas are welcome. (even the -- it's just like beagle -- kill it) approach would be fine.
Go to Configure Desktop > Desktop Search and disable it. This does not delete the index though. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/15/2010 01:32 AM, C wrote:
On Wed, Dec 15, 2010 at 04:59, David C. Rankin wrote:
Guys
Wondering why my .kde4 directory had ballooned to 2.7G, I did a du -hs on share/apps and noticed that nepomuk was eating 1.6G of space. I never use this thing and to my understanding it is still an application looking for a use. Yes, it is supposedly some generic metadata handler/index thing. So far I've never found a use for it. However, I'm concerned that it is one of those things that is integrated into everything like windows explorer and I don't know if I can just turn it off without further destabilizing kde4.
If I can turn it off, how do you do it? If I can't, then how can I tell it to only use 50M or so? 1.6G is just nuts. I suspect many of you have much larger indexes. Has anyone looked to tone this thing down and keep the index size smaller?
All ideas are welcome. (even the -- it's just like beagle -- kill it) approach would be fine.
Go to Configure Desktop> Desktop Search and disable it. This does not delete the index though.
C.
Thanks C & Rodney, I found the setting, now I'll kill it and see what happens. I suspect I'll get some performance back. Hopefully that will help with the focus lagging behind the mouse so bad. I use 'focus follows mouse' as the model and it really seems like kde4 struggles to keep up. You move the mouse across konqueror in detailed view and you can see the focus lag 1-2 files behind the mouse. I'll let you know if offloading nepomuk makes any difference. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Dec 15, 2010 at 09:04, David C. Rankin wrote:
I found the setting, now I'll kill it and see what happens. I suspect I'll get some performance back. Hopefully that will help with the focus lagging behind the mouse so bad. I use 'focus follows mouse' as the model and it really seems like kde4 struggles to keep up. You move the mouse across konqueror in detailed view and you can see the focus lag 1-2 files behind the mouse. I'll let you know if offloading nepomuk makes any difference.
With Nepomuk/Strigi switched on... I would see a significant performance hit for about 10 minutes after a restart when it would go and re-index everything it had already indexed. After that I never notice that it's running. That said.. I've switched it off, because I got annoyed by the 100% CPU hit for 10 minutes after restarting KDE. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 15 Dec 2010 14:00:45 +0530, C
With Nepomuk/Strigi switched on... I would see a significant performance hit for about 10 minutes after a restart when it would go and re-index everything it had already indexed. After that I never notice that it's running. That said.. I've switched it off, because I got annoyed by the 100% CPU hit for 10 minutes after restarting KDE.
similar here, but for me it's not really 100%, something less. and while with earlier KDE versions the nepomuk-related processes were actually blocking my system so that it froze for seconds, this doesn't happen anymore. i don't see the processes "niced" in the system monitor, but somehow they seem to "go out of the way" of other applications running; not sure how. (KDE 4.5.85 at present, but i've seen this improvement with 4.5.x already.) -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Dec 15, 2010 at 10:33, phanisvara das wrote:
On Wed, 15 Dec 2010 14:00:45 +0530, C wrote:
With Nepomuk/Strigi switched on... I would see a significant performance hit for about 10 minutes after a restart when it would go and re-index everything it had already indexed. After that I never notice that it's running. That said.. I've switched it off, because I got annoyed by the 100% CPU hit for 10 minutes after restarting KDE.
similar here, but for me it's not really 100%, something less. and while with earlier KDE versions the nepomuk-related processes were actually blocking my system so that it froze for seconds, this doesn't happen anymore. i don't see the processes "niced" in the system monitor, but somehow they seem to "go out of the way" of other applications running; not sure how. (KDE 4.5.85 at present, but i've seen this improvement with 4.5.x already.)
I should clarify.. it doesn't block up my system... I can still use it while it's indexing (ie it's nothing like Beagle was)... I just get annoyed that it runs all cores at 100%, and my system fans all switch to high... the noise is really annoying. Once it stops its redundant re-indexing (something I think is incredibly dumb since it's already indexed everything I told it to index) then my system settles down and the fans all go quiet. I wish these tools could be set to run during a "quiet" time of low activity instead of right when the system starts up. I don't mind having Nepomuk/Strigi running if it behaves, and post-indexing, it does behave (on KDE4.6)... but that indexing stage on every single startup... my laptop almost goes up in flames before it's done indexing and the poor fan almost spins itself out of the laptop housing, and my desktop sounds like a turbine race car for 10 minutes or so. This is why I turn it off.... C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 15 Dec 2010 15:17:12 +0530, C
I wish these tools could be set to run during a "quiet" time of low activity instead of right when the system starts up. I don't mind having Nepomuk/Strigi running if it behaves, and post-indexing, it does behave (on KDE4.6)... but that indexing stage on every single startup... my laptop almost goes up in flames before it's done indexing and the poor fan almost spins itself out of the laptop housing, and my desktop sounds like a turbine race car for 10 minutes or so. This is why I turn it off....
that sounds like a good idea, limit these processes to when the system isn't used. wouldn't surprise me if that was on the plan of the dev's somewhere--but it's still early times for the whole nepomuk thing. what annoys me is that i hardly ever use nepomuk search. it's only available in dolphin, which i hardly use. a nice interface to search & modify tags & all would be a good idea now. sometimes i turn it all off and delte the data store, but some time later i want to have a look again, and then let it running, thinking 'what the heck'... -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 15/12/10 10:47, C wrote:
On Wed, Dec 15, 2010 at 10:33, phanisvara das wrote:
On Wed, 15 Dec 2010 14:00:45 +0530, C wrote:
With Nepomuk/Strigi switched on... I would see a significant performance hit for about 10 minutes after a restart when it would go and re-index everything it had already indexed. After that I never notice that it's running. That said.. I've switched it off, because I got annoyed by the 100% CPU hit for 10 minutes after restarting KDE.
similar here, but for me it's not really 100%, something less. and while with earlier KDE versions the nepomuk-related processes were actually blocking my system so that it froze for seconds, this doesn't happen anymore. i don't see the processes "niced" in the system monitor, but somehow they seem to "go out of the way" of other applications running; not sure how. (KDE 4.5.85 at present, but i've seen this improvement with 4.5.x already.)
I should clarify.. it doesn't block up my system... I can still use it while it's indexing (ie it's nothing like Beagle was)... I just get annoyed that it runs all cores at 100%, and my system fans all switch to high... the noise is really annoying. Once it stops its redundant re-indexing (something I think is incredibly dumb since it's already indexed everything I told it to index) then my system settles down and the fans all go quiet.
The 100% cpu usage is a bug in the virtuoso DB used by nepomuk for storage that we're trying to track down. It seems to be a relational query that makes virtuoso spin for a few minutes, that we will report as a bug to virtuoso or modify the query for. If you want to help, install virtuoso-server from home:wstephenson:branches:KDE:Distro:Factory and next time it happens * read the port in use by virtuoso by looking at the most recent config file in /tmp/virtuoso* * connect to virtuoso: isql -H localhost -P <port> -U dba -P dba * "status();" * and let me know the output Thanks Will -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Dec 15, 2010 at 11:37, Will Stephenson wrote:
I should clarify.. it doesn't block up my system... I can still use it while it's indexing (ie it's nothing like Beagle was)... I just get annoyed that it runs all cores at 100%, and my system fans all switch to high... the noise is really annoying. Once it stops its redundant re-indexing (something I think is incredibly dumb since it's already indexed everything I told it to index) then my system settles down and the fans all go quiet.
The 100% cpu usage is a bug in the virtuoso DB used by nepomuk for storage that we're trying to track down. It seems to be a relational query that makes virtuoso spin for a few minutes, that we will report as a bug to virtuoso or modify the query for.
If you want to help, install virtuoso-server from home:wstephenson:branches:KDE:Distro:Factory and next time it happens
* read the port in use by virtuoso by looking at the most recent config file in /tmp/virtuoso* * connect to virtuoso: isql -H localhost -P <port> -U dba -P dba * "status();" * and let me know the output
Cool, I'll give that a try later today. Just to be sure for those reading this thread and still hurting from their Beagle experience... Nepomuk does behave well (CPU and system I/O performance is not hit) once it has gotten past the initial CPU usage on start up thing. You don't notice it's there after it's done indexing - even on a low end machine (I use/test it on an EEE netbook as well). What about the vast amounts of disk space it chews up for the indexing? On my server/desktop machine, I've got it severely restricted what it can index (only a few directories with images, documents and multimedia files) and the Nepomuk index is over 1Gb, and David noted an even larger index. Is it "normal" for the index to grow this big? I've never turned on the backup/snapshot feature, so in theory, it shouldn't be multiple backup copies that it's using. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 15 Dec 2010 16:07:58 +0530, Will Stephenson
If you want to help, install virtuoso-server from home:wstephenson:branches:KDE:Distro:Factory and next time it happens * read the port in use by virtuoso by looking at the most recent config file in /tmp/virtuoso* * connect to virtuoso: isql -H localhost -P <port> -U dba -P dba * "status();" * and let me know the output
i got the port from the latest of several "virtuoso_xyz-etc.ini". the following is what i got for my trouble. does that tell you anything, or was i too late (one of my 2 CPU's was already slowing down): ----------- phani:/home/phani # isql -H localhost -P 1120 0U dba -P dba * "status()" isql: Max. 22 files can be specified at the command line, ignoring all files from skype-repo.txt onward. The function gethostbyname returned error 0 for host "0U". *** Error S2801: [Virtuoso Driver]CL033: Connect failed to 0U:1111 = 0U:1111. at line 0 of Top-Level: phani:/home/phani # ----------- (same result as user or root.) -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 15 Dec 2010 22:30:46 +0530, phanisvara das
----------- phani:/home/phani # isql -H localhost -P 1120 0U dba -P dba * "status()"
just saw there was a typo; it's not "OU dba" but "-U dba". but that produces the same result; only the file names "ignoring all files from..." changes. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 15 Dec 2010 22:35:19 +0530, phanisvara das
just saw there was a typo; ...
found more mistakes i made, but the result remains pretty much the same. my last command line: ----------- isql -H localhost -S 1122 -U dba -P dba * "status();" ----------- seems you (will s.) also made a mistake. the command you specified reads: ----------- * read the port in use by virtuoso by looking at the most recent config file in /tmp/virtuoso* * connect to virtuoso: isql -H localhost -P <port> -U dba -P dba * "status();" ----------- you specify sever port with "-P", which is, according to "isql --help" (and yourself later on) used for the password. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 15 Dec 2010 18:25:15 phanisvara das wrote:
On Wed, 15 Dec 2010 22:35:19 +0530, phanisvara das
wrote: just saw there was a typo; ...
found more mistakes i made, but the result remains pretty much the same. my last command line:
----------- isql -H localhost -S 1122 -U dba -P dba * "status();" -----------
seems you (will s.) also made a mistake. the command you specified reads:
----------- * read the port in use by virtuoso by looking at the most recent config file in /tmp/virtuoso* * connect to virtuoso: isql -H localhost -P <port> -U dba -P dba * "status();" -----------
you specify sever port with "-P", which is, according to "isql --help" (and yourself later on) used for the password.
Sorry. isql -H localhost -S <port> -U dba -P dba -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Mittwoch, 15. Dezember 2010, 10:47:12 schrieb C:
I should clarify.. it doesn't block up my system... I can still use it while it's indexing (ie it's nothing like Beagle was)... I just get annoyed that it runs all cores at 100%, and my system fans all switch to high... the noise is really annoying. Once it stops its redundant re-indexing (something I think is incredibly dumb since it's already indexed everything I told it to index) then my system settles down and the fans all go quiet.
Apparently it has to scan all folders again in order to find all kind of changes: https://bugs.kde.org/show_bug.cgi?id=182064 Sven -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Mittwoch, 15. Dezember 2010, 04:59:17 schrieb David C. Rankin:
Wondering why my .kde4 directory had ballooned to 2.7G, I did a du -hs on share/apps and noticed that nepomuk was eating 1.6G of space.
It seems it never ever removes any items from its index thus it never shrinks. https://bugs.kde.org/show_bug.cgi?id=252676 The only way to keep the index small is to turn off strigi and only leave nepomuk enabled. You can delete the index-db. Sven -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
C
-
David C. Rankin
-
phanisvara das
-
Rodney Baker
-
Sven Burmeister
-
Will Stephenson