unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: guile-user@gnu.org
Subject: Re: [Wikidata] [ANN] nomunofu v0.1.0
Date: Mon, 23 Dec 2019 09:56:17 +0100	[thread overview]
Message-ID: <20191223085617.GA14347@tuxteam.de> (raw)
In-Reply-To: <3C3055B6-0BDC-444B-832F-C67477535E35@openlinksw.com>

[-- Attachment #1: Type: text/plain, Size: 1727 bytes --]

On Sun, Dec 22, 2019 at 06:36:06PM -0500, Ted Thibodeau Jr via General Guile related discussions wrote:

[...]

> Hi, Amirouche --
> 
> Kingsley's points about tuning Virtuoso to use available 
> RAM [1] and other system resources are worth looking into, 
> but a possibly more important first question is --
> 
>    Exactly what version of Virtuoso are you testing?
> 
> If you followed the common script on Ubuntu 18.04, i.e., --
> 
>    sudo apt update
> 
>    sudo apt install virtuoso-opensource

Hi, Ted

I see you do have a stake in the game. That's fine, since having
a good technical discussion should be independent of that. So
thanks for chiming in!

> -- then you likely have version 6.1.6 of VOS, the Open Source 
> Edition of Virtuoso, which shipped 2012-08-02 [2], and is far
> behind the latest version of both VOS (v7.2.5+) and Enterprise 
> Edition (v8.3+)!

Wouldn't that be something your company could contribute to
Ubuntu/Debian? Contact the package maintainers and help keeping
the free version of Virtuoso up to snuff on those platforms?

A rising tide, etc?

> You can also try Enterprise Edition at no cost for 30 days [5].

I think it's somewhat unfair to try to compare a freshly
done free project with an established commercial one.

> I'll be interested to hear your new results, with a current build,
> and with proper INI tuning in place.

Why not assist Amirouche on that part? After all, you have
much easier access to Virtuoso expertise, and me, at least,
rather prefer Amirouche to spend his time tuning his wonderful
free creatures than tuning Virtuoso ;-P (of course, he'll end
up doing what he enjoys most, I'd hope!).

Cheers
-- tomás

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2019-12-23  8:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-08 17:52 [ANN] nomunofu v0.1.0 Amirouche Boubekki
     [not found] ` <CAL7_Mo_iaGff9qPOq7ic0i3epwd0wR-JKJcRAy_q4et5Lgo=bg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-12-10  9:52   ` Amirouche Boubekki
2019-12-12 14:57     ` Amirouche Boubekki
2019-12-12 15:57       ` tomas
2019-12-16 12:49         ` Amirouche Boubekki
2019-12-22 20:17     ` Amirouche Boubekki
     [not found]       ` <CAL7_Mo_JxZjrrXQzE99nKgoZ94mVrbQLMT+15Gb9PwioOFQVkw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-12-22 23:36         ` Ted Thibodeau Jr
2019-12-23  8:56           ` tomas [this message]
2019-12-23 12:34             ` [Wikidata] " Roel Janssen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191223085617.GA14347@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).