unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Ted Thibodeau Jr <tthibodeau-HpHEqLDO2a7UEDaH6ef/NA@public.gmane.org>
To: Discussion list for the Wikidata project
	<wikidata-RusutVdil2icGmH+5r0DM0B+6BGkLq7r@public.gmane.org>
Cc: Guile User <guile-user-mXXj517/zsQ@public.gmane.org>,
	semantic-web <semantic-web-Pl0VvzL1eo4@public.gmane.org>
Subject: Re: [ANN] nomunofu v0.1.0
Date: Sun, 22 Dec 2019 18:36:06 -0500	[thread overview]
Message-ID: <3C3055B6-0BDC-444B-832F-C67477535E35@openlinksw.com> (raw)
In-Reply-To: <CAL7_Mo_JxZjrrXQzE99nKgoZ94mVrbQLMT+15Gb9PwioOFQVkw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 4284 bytes --]


On Dec 22, 2019, at 03:17 PM, Amirouche Boubekki <amirouche.boubekki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
> Hello all ;-)
> 
> 
> I ported the code to Chez Scheme to do an apple-to-apple comparison
> between GNU Guile and Chez and took the time to launch a few queries
> against Virtuoso available in Ubuntu 18.04 (LTS).

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

-- 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+)!

The easiest way to confirm what you're running is to review 
the first "paragraph" of output from the command corresponding 
to the name of your Virtuoso binary --

   virtuoso-t -?

   virtuoso-iodbc-t -?

If I'm right, and you're running 6.x, you'll get much better
test results just by running a current version of Virtuoso.

You can build VOS 7.2.6+ from source [3] (we'd recommend the 
develop/7 branch [4] for the absolute latest), or download a 
precompiled binary [5] of VOS 7.2.5.1 or 7.2.6.dev.

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



[1] http://vos.openlinksw.com/owiki/wiki/VOS/VirtRDFPerformanceTuning

[2] http://vos.openlinksw.com/owiki/wiki/VOS/VOSNews2012#2012-08-02%20--%20Announcing%20Virtuoso%20Open-Source%20Edition%20v6.1.6.

[3] http://vos.openlinksw.com/owiki/wiki/VOS/VOSBuild

[4] https://github.com/openlink/virtuoso-opensource/tree/develop/7

[5] https://sourceforge.net/projects/virtuoso/files/virtuoso/ 





> Spoiler: the new code is always faster.
> 
> The hard disk is SATA, and the CPU is dubbed: Intel(R) Xeon(R) CPU
> E3-1220 V2 @ 3.10GHz
> 
> I imported latest-lexeme.nt (6GB) using guile-nomunofu, chez-nomunofu
> and Virtuoso:
> 
> - Chez takes 40 minutes to import 6GB
> - Chez is 3 to 5 times faster than Guile
> - Chez is 11% faster than Virtuoso


How did you load the data?  Did you use Virtuoso's build-load
facilities?  This is the recommended method [6].

[6] http://vos.openlinksw.com/owiki/wiki/VOS/VirtBulkRDFLoader


> Regarding query time, Chez is still faster than Virtuoso with or
> without cache.  The query I am testing is the following:
> 
> SELECT ?s ?p ?o
> FROM <http://fu>
> WHERE {
>  ?s <http://purl.org/dc/terms/language> <http://www.wikidata.org/entity/Q150> .
>  ?s <http://wikiba.se/ontology#lexicalCategory>
> <http://www.wikidata.org/entity/Q1084> .
>  ?s <http://www.w3.org/2000/01/rdf-schema#label> ?o
> };
> 
> Virtuoso first query takes: 1295 msec.
> The second query takes: 331 msec.
> Then it stabilize around: 200 msec.
> 
> chez nomunofu takes around 200ms without cache.
> 
> There is still an optimization I can do to speed up nomunofu a little.
> 
> 
> Happy hacking!


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

Regards,

Ted



--
A: Yes.                          http://www.idallen.com/topposting.html
| Q: Are you sure?           
| | A: Because it reverses the logical flow of conversation.
| | | Q: Why is top posting frowned upon?

Ted Thibodeau, Jr.           //               voice +1-781-273-0900 x32
Senior Support & Evangelism  //        mailto:tthibodeau-HpHEqLDO2a7UEDaH6ef/NA@public.gmane.org
                             //              http://twitter.com/TallTed
OpenLink Software, Inc.      //              http://www.openlinksw.com/
         20 Burlington Mall Road, Suite 322, Burlington MA 01803
     Weblog    -- http://www.openlinksw.com/blogs/
     Community -- https://community.openlinksw.com/
     LinkedIn  -- http://www.linkedin.com/company/openlink-software/
     Twitter   -- http://twitter.com/OpenLink
     Facebook  -- http://www.facebook.com/OpenLinkSoftware
Universal Data Access, Integration, and Management Technology Providers





[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2094 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

  parent reply	other threads:[~2019-12-22 23:36 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 [this message]
2019-12-23  8:56           ` [Wikidata] " tomas
2019-12-23 12:34             ` 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=3C3055B6-0BDC-444B-832F-C67477535E35@openlinksw.com \
    --to=tthibodeau-hpheqldo2a7uedah6ef/na@public.gmane.org \
    --cc=guile-user-mXXj517/zsQ@public.gmane.org \
    --cc=semantic-web-Pl0VvzL1eo4@public.gmane.org \
    --cc=wikidata-RusutVdil2icGmH+5r0DM0B+6BGkLq7r@public.gmane.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).