Hi,

I'm using a self-compiled version of Virtuoso OpenSource 6.1.1 on a Ubuntu 10.04 LTS Lucid Lynx x64 installation on a Core2Duo machine. I can't finished 'make check' successfully, but so far the instance works well.

Cheers,

Bob

PS: Sorry Hugh, for doubling this E-Mail

Am 12.06.2010 18:37, schrieb Hugh Williams:
Hi Peter,

Virtuoso open source and commercial are fully multi-threaded products,
with the number of threads used by the server being configurable and
determining the memory usage of the server as detailed at:

http://docs.openlinksw.com/virtuoso/dbadm.html#srvadmopreq

In terms of multiple processor/core usage this would be determined by
the operation system which should schedule the execution of the threads
in use equally across the available processors/cores.

Best Regards
Hugh Williams
Professional Services
OpenLink Software
Web: http://www.openlinksw.com
Support: http://support.openlinksw.com
Forums: http://boards.openlinksw.com/support
Twitter: http://twitter.com/OpenLink

On 12 Jun 2010, at 00:14, Peter DeVries wrote:

I have not started yet, VOS is now included in the Ubuntu packages and
it works with a regular server setup.

sudo apt-get *virtuoso-opensource*

I did just noticed that Eucalyptus will use just one VM per processor
so it might be best to go with the regular Lucid server.

To what extent does Virtuoso Open Source benefit from multiple processors?

Thanks!

- Pete


On Fri, Jun 11, 2010 at 5:16 PM, Nathan <[email protected]
<mailto:[email protected]>> wrote:

    Peter DeVries wrote:

        Hi have a new server that I am thinking of setting up with
        Virtuoso Open
        Source under Ubuntu Lucid Server Eucalyptus.

        I have been able to get Virtuoso Open Source running under
        Ubuntu Lucid
        server via the apt package.

        Does anyone have any experience getting this to work under
        Eucalyptus? Any
        tips or suggestions?


    Have you tried a normal .configure and make ?
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

Reply via email to