W3C home > Mailing lists > Public > public-lod@w3.org > September 2018

Re[2]: Release of SAGE 1.0: a stable, responsive and unrestricted SPARQL query server

From: Paul Houle <ontology2@gmail.com>
Date: Fri, 07 Sep 2018 18:54:18 +0000
To: "Kingsley Idehen" <kidehen@openlinksw.com>, public-lod@w3.org
Message-Id: <em415f157a-8c19-4126-aa77-fbe9a5a4367c@pendragon>
I will tell you how they make that claim,  and it is because they can 
persist the status of an incomplete query and send it back to the sender 
as a backstop when the system decides it doesn't have capacity to work 
on that query at the moment.  It is easier for them to do that because 
it is a read-only database.

The way you might break it is that if the query state is large,  then 
the process of handling it might be too much.

People are doing interesting things with "reactive systems" that 
incorporate load shedding mechanisms so that they stay responsive even 
under overload.

------ Original Message ------
From: "Kingsley Idehen" <kidehen@openlinksw.com>
To: public-lod@w3.org
Sent: 9/7/2018 10:44:08 AM
Subject: Re: Release of SAGE 1.0: a stable, responsive and unrestricted 
SPARQL query server

>On 9/7/18 9:44 AM, Pascal Molli wrote:
>>Dear Semantic Web, Linked Data Community,
>>
>>
>>We are proud to announce the release of SAGE 1.0, a stable, responsive 
>>and unrestricted SPARQL query server [1]. The software and an online 
>>demo are freely available at:
>>
>>
>>http://sage.univ-nantes.fr/
>>
>
>Hi Pascal,
>
>Congrats!
>
>>
>>Compared to public SPARQL endpoints, SAGE is stable and responsive 
>>without quotas.
>>
>
>What does that mean?
>
>>SAGE is able to deliver complete results for any SPARQL query. The 
>>Sage engine outperforms a Virtuoso server in term of execution time 
>>when the server load increases.
>>
>
>What does that mean?
>
>How can I or anyone else verify this claim?
>
>What is your live SPARQL Query Service endpoint URI?
>
>>
>>Compared to the Linked Data Fragment approach, SAGE outperforms a TPF 
>>server in term of execution time, communication costs and data 
>>transfers by several order of magnitude by processing BGP on the 
>>server side.
>>
>>
>>Experimental results and more details are available in [1].
>>
>
>Do you offer a live SPARQL endpoint?  I am eager to test your claims.
>
>>
>>We encourage you to run complex queries on RDF datasets available on 
>>the demo server and check performance (many presets queries are 
>>available).
>>
>>
>>We appreciate your feedback/comments/questions to be sent to our 
>>mailing list [2] or our issue tracker on github [3].
>>
>>
>>On behalf of the Sage team,
>>
>>---
>>
>>Pascal Molli, Hala-Skaf-Molli, Thomas Minier - GDD Team 
>><https://sites.google.com/site/gddlina/home>, LS2N 
>><https://www.ls2n.fr/?lang=en>, University of Nantes 
>><http://www.univ-nantes.fr/>.
>>
>>
>>[1] Thomas Minier, Hala Skaf-Molli, Pascal Molli. SaGe: Preemptive 
>>Query Execution for High Data Availability on the Web. 2018. 
>>https://hal.archives-ouvertes.fr/hal-01806486v1
>>
>>
>>[2] sage@univ-nantes.fr
>>
>>
>>[3] https://github.com/sage-org/sage-engine/issues
>>
>>
>
>
>--
>Regards,
>
>Kingsley Idehen	
>Founder & CEO
>OpenLink Software   (Home Page: http://www.openlinksw.com)
>
>Weblogs (Blogs):
>Legacy Blog: http://www.openlinksw.com/blog/~kidehen/
>Blogspot Blog: http://kidehen.blogspot.com
>Medium Blog: https://medium.com/@kidehen
>
>Profile Pages:
>Pinterest: https://www.pinterest.com/kidehen/
>Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen
>Twitter: https://twitter.com/kidehen
>Google+: https://plus.google.com/+KingsleyIdehen/about
>LinkedIn: http://www.linkedin.com/in/kidehen
>
>Web Identities (WebID):
>Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i
>         : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this
Received on Friday, 7 September 2018 18:54:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:22:47 UTC