Summary: | Just login and logout - 165 MB disk space in $HOME used (Akonadi and Nepomuk data) | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Christoph Feck <cfeck> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | normal | CC: | kairo, kdepim-bugs, lameventanas, sebastian, trueg, vkrause |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Christoph Feck
2009-12-02 04:29:07 UTC
24MB of Nepomuk data is totally normal. All installed ontologies are loaded into the database. There is no way around that. I know that this is not a valid argument for many people but 24MB is nothing today. My harddisk has 1TB! From my side (Nepomuk) this is a "wontfix"/"cantfix". Hm, the KDEDIR/share/ontology folder is just 644K. I hope it is just the ontologies that blow up by a factor of 40, not all indexes/annotations. 24 Mb is a lot of space, maybe just not to you and your 1 user system with 1 Tb hard drive, but what about workstation networks mounting $HOME from NFS and limited space and quotas? Why not make Nepomuk, Akonadi, Soprano, Redland etc. (all of the semantic desktop thing) optional dependencies of KDE? I was able to resize the ib_logfile0/1 files from 64 MB each to 2 MB each by using the mobile database profile. This way, the total size used is reduced from 165 MB to 41 MB, which is a 75% reduction of the previous size. Still I think these files should be in a temporary directory, not in user's home. I do not know how the reduced size affects the performance of Akonadi, as I am still using KMail from 4.4 branch, which is said to not use Akonadi. Since I switched Akonadi to use the QSQLITE database driver, the only issue is Nepomuk. As far as I grasp the features of the Virtuoso database, it is not possible to replace the Nepomuk storage with a "simpler" database, such as sqlite, so this is a WONTFIX (see comment #1). Don't get me wrong: I would like to improve this and as soon as I come accross a good idea I will try it. But so far I simply have no solution. |