MySQL problems solved by switching to Virtuoso

[jasenj1]

I'm running an ontology with about 150k triples. There's only about a
dozen classes and properties, and I don't think their definitions are
very complicated. Using MySQL performance was pretty bad. Some basic
browsing would take several seconds to return results, and there were
a few objects that if I tried to browse them would send MySQL off
into endless 100% CPU utilization.

So I broke down and installed Virtuoso. It performs much better. The
queries that would kill MySQL return quickly. There's still some
issues related to directory permissions, but basic functionality seems
solid. I can't get it to work on my OS X box, but it's working on a
Windows machine - good enough for now.

- Jasen.

[Sebastian Dietzold]

quote jasenj1 (3.12.2009):

> I'm running an ontology with about 150k triples. There's only about a
> dozen classes and properties, and I don't think their definitions are
> very complicated. Using MySQL performance was pretty bad. Some basic
> browsing would take several seconds to return results, and there were a
> few objects that if I tried to browse them would send MySQL off into
> endless 100% CPU utilization.

I think, thats the "copy to tmp table problem" ...

> So I broke down and installed Virtuoso. It performs much better. The
> queries that would kill MySQL return quickly. There's still some issues
> related to directory permissions, but basic functionality seems solid. I
> can't get it to work on my OS X box, but it's working on a Windows
> machine - good enough for now.

We're using virtuoso on MacOSX as well. Here is a tutorial on how to
install it
http://code.google.com/p/ontowiki/wiki/UsingOntoWikiWithVirtuoso

There are also some specific MaxOSX paragraphs ...

SD


--
Sebastian Dietzold - Department of Computer Science; University of Leipzig
Tel/Fax: +49 341 97 323-66/-29 http://bis.uni-leipzig.de/SebastianDietzold