[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 246678] virtuoso: Usage of CPU is much too high
From:       Alejandro Nova <alejandronova () gmail ! com>
Date:       2012-01-17 0:35:09
Message-ID: E1Rmx13-0002Vt-6b () bugs ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=246678





--- Comment #121 from Alejandro Nova <alejandronova gmail com>  2012-01-17 00:35:08 ---
Basically this issue connects several bugs. Some of the most memorable ones
are:

- Virtuoso being locked up with strigi, one core sleeping - killed with KDE
4.6.1.
- Various memory leaks, some with Virtuoso, some with nepomukstorage, and even
some with dbus-daemon. The last one of those was fixed with Soprano 2.7.3.
- Virtuoso being locked up with akonadi-nepomuk-email-feeder, one core wasted.
That one haunted KDE 4.7.x until ~4.7.4.
- Virtuoso being locked up with akonadi-nepomuk-feeder, one core wasted. That
is the latest incarnation of this bug, and is what richb1908@gmail.com was
experiencing.

All of these real issues were amplified by more downstream issues.

- Strigi lacks a real release policy. During most of 2010 and part of 2011,
Debian shipped Strigi 0.7.2, an extremely buggy and ancient release.
- Akonadi and Soprano are not updated with KDE, in KDE dependent distros.

So, you can't really fix this, unless:

- You require a Virtuoso + Soprano + Akonadi + Strigi + Shared Desktop
Ontologies stack, and maintain it with a KDE 4.x release cycle.
- You assign a real maintainer to akonadi-nepomuk-feeder (that package is
somewhat orphan, unlike Nepomuk).
- You REQUIRE distros shipping KDE to UPDATE their packages. That can be made
easily through CMakeFiles (if you ship KDE 4.8, then you must have certain
versions of Soprano, Akonadi, Strigi and shared-desktop-ontologies)
- You MAKE a "Update my Ontologies" app like what Bangarang has. That's a
necessity.

Once you have all of this sorted out, you can really begin with bug triaging
and reporting. Reporting bugs without all of these requirements unmet will be a
waste of time for the reporter and for the developer.

About the Nepomuk database erasing: if I read correctly Sebastian Trueg's blogs
and dev history, KDE SC 4.8 is going to be the last release that will require
erasing everything to work well. The Akonadi Nepomuk Feeder is fresh code, made
with something called DMS (AFAIK, replacing hand tuned SQL queries with queries
generated automatically)

Please, be more constructive about how to fix this. I really hate Nepomuk bugs,
I really want the thing to work, but we won't get anywhere if we just kill the
thing. Remember that Nepomuk is the very thing (WinFS) that Microsoft FAILED to
implement, and Sebastian Trueg has made tremendous strides to do what 
Microsoft failed to do, with no resources, and (as of late) with no money.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]