Comments on: Virtuoso, here I come! http://satellite.vizZzion.org/blog/2009/10/virtuoso-here-i-come/ Sebastian Kügler's web log Mon, 06 Sep 2010 11:08:08 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: trooper http://satellite.vizZzion.org/blog/2009/10/virtuoso-here-i-come/comment-page-1/#comment-62 trooper Wed, 21 Oct 2009 10:54:47 +0000 http://vizZzion.org/blog/2009/10/virtuoso-here-i-come/#comment-62 My biggest problem setting up was getting other KDE components to compile, including kdebase (kde svn was a mess of broken compiles when I did it). Finally got it going and seemed to convert ok. I have 5gb index and 500mb metadata. Strigi still seemingly stalls indefinitely parsing certain directories. Dolphin froze randomly browsing and using nepomuksearch:/ guaranteed, occasionally. But when it is working right, virtuoso is visibly much better performance than sesame2 and Dolphin/gwenview were actually usable again though a little laggy. Still work to go, but a great improvement. My biggest problem setting up was getting other KDE components to compile, including kdebase (kde svn was a mess of broken compiles when I did it). Finally got it going and seemed to convert ok. I have 5gb index and 500mb metadata. Strigi still seemingly stalls indefinitely parsing certain directories. Dolphin froze randomly browsing and using nepomuksearch:/ guaranteed, occasionally. But when it is working right, virtuoso is visibly much better performance than sesame2 and Dolphin/gwenview were actually usable again though a little laggy. Still work to go, but a great improvement.

]]> By: Eduardo Robles Elvira http://satellite.vizZzion.org/blog/2009/10/virtuoso-here-i-come/comment-page-1/#comment-60 Eduardo Robles Elvira Tue, 20 Oct 2009 09:28:44 +0000 http://vizZzion.org/blog/2009/10/virtuoso-here-i-come/#comment-60 I have already compiled virtuoso support without having it installed because it's a runtime dep, so I don't think I need to rebuild kdesupport, and then I wonder why should I rebuild kdebase, i.e. is there anything in kdebase that depends directly on the virtuoso backend? Sounds unlikely. Anyway I'll try to switch to Virtuoso too, thanks for the howto Sebas =). I have already compiled virtuoso support without having it installed because it’s a runtime dep, so I don’t think I need to rebuild kdesupport, and then I wonder why should I rebuild kdebase, i.e. is there anything in kdebase that depends directly on the virtuoso backend? Sounds unlikely. Anyway I’ll try to switch to Virtuoso too, thanks for the howto Sebas =).

]]> By: Anon http://satellite.vizZzion.org/blog/2009/10/virtuoso-here-i-come/comment-page-1/#comment-58 Anon Mon, 19 Oct 2009 20:45:26 +0000 http://vizZzion.org/blog/2009/10/virtuoso-here-i-come/#comment-58 " Redland is written in C++" Actually straight C, as far as I can tell. ” Redland is written in C++”

Actually straight C, as far as I can tell.

]]> By: lbbros.myopenid.com/ http://satellite.vizZzion.org/blog/2009/10/virtuoso-here-i-come/comment-page-1/#comment-57 lbbros.myopenid.com/ Mon, 19 Oct 2009 20:40:00 +0000 http://vizZzion.org/blog/2009/10/virtuoso-here-i-come/#comment-57 Does this also work with non-trunk (i.e. 4.3 branch)? I gave a try with a newer version of Soprano and Virtuoso, but no dice. I just managed to crash nepomukserver if I asked for the backend. Does this also work with non-trunk (i.e. 4.3 branch)? I gave a try with a newer version of Soprano and Virtuoso, but no dice. I just managed to crash nepomukserver if I asked for the backend.

]]> By: flickr.com/photos/wste… http://satellite.vizZzion.org/blog/2009/10/virtuoso-here-i-come/comment-page-1/#comment-56 flickr.com/photos/wste… Mon, 19 Oct 2009 19:40:51 +0000 http://vizZzion.org/blog/2009/10/virtuoso-here-i-come/#comment-56 openSUSE users can get the packages to build and run the Virtuoso backend (including minimal 5.0.12 packages) by registering KDE:KDE4:UNSTABLE:Desktop and installing virtuoso-drivers and libiodbc-devel. openSUSE users can get the packages to build and run the Virtuoso backend (including minimal 5.0.12 packages) by registering KDE:KDE4:UNSTABLE:Desktop and installing virtuoso-drivers and libiodbc-devel.

]]>