I am seeing the following problem appearing on random occasions during regular usage of my regular updated KDE/F14/64bit system.
The desktop becomes extremely slow and unresponsive, out of the blue. It lasts for about a minute or two, and then reverts to normal. If i happen to have a terminal open when it happens, I can see in top that usage of both CPUs goes to 100%. However, it's not because some process is using them, but because both CPUs are wasting cycles in "wait" state for I/O.
Then if I manage to start iotop to see what is sucking all disk I/O, I see that 99.99% of I/O is being used by something like
virtuoso-t +foreground +configfile /tmp/virtuoso_Lh1825.ini +wait
Would someone explain what is this, why is it running on random, what triggers it, and --- most importantly --- why is it configured by default to suck all life out of my system during its (presumably normal) operation?
yum info virtuoso-opensource says:
Summary : A high-performance object-relational SQL database Description : Virtuoso is a scalable cross-platform server that combines SQL/RDF/XML Data Management with Web Application Server and Web Services Platform functionality.
This suggests that it is some kind of database used by KDE (or something else?), so I can understand that it can be resource-hungry. However, I don't understand what is its purpose on my system?
If I try to yum remove it, it wants to remove most of the OS istallation, including kdebase, so I guess it is something very required by KDE.
I would be very thankful if someone explains what this is and how to make it do its work only when the system is idle enough (say, when the screensaver has been active for half an hour, or something like that), and not in the middle of my regular work.
TIA, :-) Marko
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 21.03.2011 23:57, schrieb Marko Vojinovic:
I would be very thankful if someone explains what this is and how to make it do its work only when the system is idle enough (say, when the screensaver has been active for half an hour, or something like that), and not in the middle of my regular work.
TIA, :-) Marko
I think it's the database used by Strigi, which is used by Nepomuk to index files and meta data for the desktop search. So if you'd disable Nepomuk/Semantic Desktop in the system settings, it should stop running. There should be an icon in the system tray as well I think.
Regards, Julian
On Tuesday, March 22, 2011 03:28:09 PM Julian Aloofi wrote:
Am 21.03.2011 23:57, schrieb Marko Vojinovic:
I would be very thankful if someone explains what this is and how to make it do its work only when the system is idle enough (say, when the screensaver has been active for half an hour, or something like that), and not in the middle of my regular work.
TIA, :-) Marko
I think it's the database used by Strigi, which is used by Nepomuk to index files and meta data for the desktop search. So if you'd disable Nepomuk/Semantic Desktop in the system settings, it should stop running. There should be an icon in the system tray as well I think.
It's called nepomukcontroller (Nepomuk File Indexing Controller in menu).
R.
Regards, Julian _______________________________________________ kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
On Tuesday 22 March 2011 14:28:09 Julian Aloofi wrote:
Am 21.03.2011 23:57, schrieb Marko Vojinovic:
I would be very thankful if someone explains what this is and how to make it do its work only when the system is idle enough (say, when the screensaver has been active for half an hour, or something like that), and not in the middle of my regular work.
I think it's the database used by Strigi, which is used by Nepomuk to index files and meta data for the desktop search. So if you'd disable Nepomuk/Semantic Desktop in the system settings, it should stop running. There should be an icon in the system tray as well I think.
Right, thanks! :-)
I disabled Nepomuk, with the hope that it will fix this issue. I am not exactly sure what is Nepomuk even supposed to do, and what "semantic desktop search" means at all, so I hope I won't need its services. ;-) It appears it is configured to index only the ~/Desktop directory, which is empty (bar two icons), so in this sense it is quite useless for me.
Best, :-) Marko
On Tuesday, March 22, 2011 03:55:28 PM Marko Vojinovic wrote:
On Tuesday 22 March 2011 14:28:09 Julian Aloofi wrote:
Am 21.03.2011 23:57, schrieb Marko Vojinovic:
I would be very thankful if someone explains what this is and how to make it do its work only when the system is idle enough (say, when the screensaver has been active for half an hour, or something like that), and not in the middle of my regular work.
I think it's the database used by Strigi, which is used by Nepomuk to index files and meta data for the desktop search. So if you'd disable Nepomuk/Semantic Desktop in the system settings, it should stop running. There should be an icon in the system tray as well I think.
Right, thanks! :-)
I disabled Nepomuk, with the hope that it will fix this issue. I am not exactly sure what is Nepomuk even supposed to do, and what "semantic desktop search" means at all, so I hope I won't need its services. ;-)
You can use it for example in Dolphin - Find button.
Jaroslav
It appears it is configured to index only the ~/Desktop directory, which is empty (bar two icons), so in this sense it is quite useless for me.
Best, :-) Marko
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Julian Aloofi wrote:
I think it's the database used by Strigi, which is used by Nepomuk to index files and meta data for the desktop search.
Actually, it's the database used by Nepomuk itself.
Strigi indexing is only the most resource-intensive Nepomuk task, and thus the one which will be causing most of the Virtuoso database traffic.
So if you'd disable Nepomuk/Semantic Desktop in the system settings, it should stop running.
Disabling Strigi file indexing should be sufficient to keep resource usage down. Having Nepomuk enabled is useful because other stuff wants to use it, e.g. Akonadi, which is used by kdepim. And without Strigi indexing, Nepomuk and Virtuoso should be using little to no CPU resources.
Kevin Kofler
On 03/22/2011 05:01 PM, Kevin Kofler wrote:
Disabling Strigi file indexing should be sufficient to keep resource usage down. Having Nepomuk enabled is useful because other stuff wants to use it, e.g. Akonadi, which is used by kdepim. And without Strigi indexing, Nepomuk and Virtuoso should be using little to no CPU resources.
It seems silly to allow the user to get bogged down by an indexing update. Can we arrange for these to run at a lower IO priority (bulk, perhaps) by default? Even as SCHED_IDLE maybe?
Does systemd do this stuff? <--- obviously not well informed
-Bill
On 04/06/2011 02:50 PM, Bill McGonigle wrote:
On 03/22/2011 05:01 PM, Kevin Kofler wrote:
Disabling Strigi file indexing should be sufficient to keep resource usage down. Having Nepomuk enabled is useful because other stuff wants to use it, e.g. Akonadi, which is used by kdepim. And without Strigi indexing, Nepomuk and Virtuoso should be using little to no CPU resources.
It seems silly to allow the user to get bogged down by an indexing update. Can we arrange for these to run at a lower IO priority (bulk, perhaps) by default? Even as SCHED_IDLE maybe?
Yeah, I have to say I've been pretty unhappy with the load on my system recently, I'm guessing with the shift to 4.6.1.
On Thursday 07 April 2011 04:15:34 Orion Poplawski wrote:
Yeah, I have to say I've been pretty unhappy with the load on my system recently, I'm guessing with the shift to 4.6.1.
I noticed that daily virtuoso runs initally, so the load is high, after booting the machine and entering kde and it rests after.
Other than that it works well here. :-)
On Wed, Apr 6, 2011 at 4:50 PM, Bill McGonigle wrote:
On 03/22/2011 05:01 PM, Kevin Kofler wrote:
Disabling Strigi file indexing should be sufficient to keep resource usage down. Having Nepomuk enabled is useful because other stuff wants to use it, e.g. Akonadi, which is used by kdepim. And without Strigi indexing, Nepomuk and Virtuoso should be using little to no CPU resources.
It seems silly to allow the user to get bogged down by an indexing update.
How is "indexing" defined by KDE? (seriously)
and who is its target population?
Orcan
-
Bill McGonigle -
Jaroslav Reznik -
José Abílio Matos -
Julian Aloofi -
Kevin Kofler -
Marko Vojinovic -
Orcan Ogetbil -
Orion Poplawski