Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.
Live DBpedia querying 
with high availability 
Ruben Verborgh
“If DBpedia goes down, nobody complains. 
If the BBC Linked Data Platform goes down, 
that’s a problem for live applicatio...
Despite all traffic it receives, 
DBpedia has an uptime of around 95%, 
making it one of the more reliable endpoints. 
DBp...
Public endpoints like DBpedia 
are hosted voluntarily, 
as-is and free of charge. 
Since DBpedia is hosted for free, 
we s...
The majority of the information 
on the Web is hosted voluntarily, 
as-is and free of charge. 
Wouldn’t we complain 
if th...
There’s a difference! 
DBpedia offers a SPARQL interface, 
which is much more expensive than HTTP.
Exactly. 
If DBpedia offers information 
as-is and free of charge, 
why choose such an expensive interface? 
Why does it c...
Why offer to answer complex queries 
if you cannot reliably answer simple ones?
SELECT * { ?s ?p ?o } LIMIT 1
What other interfaces 
to RDF are available? 
low server demand high server demand 
data 
dump 
SPARQL 
endpoint 
derefer-...
A triple pattern fragments interface 
is much less powerful than SPARQL. 
So also much less demanding, 
like other HTTP in...
How do we handle complex queries? 
Clients execute them! 
SELECT ?person ?city WHERE { 
?person a dbpedia-owl:Artist. 
dbp...
data processing 
server
data processing 
server client
Server CPU usage remains low. 
1 10 100 
100 
50 
0 
clients 
Fig. 3.3: Query timeouts 
10 100 
100 
50 
0 
clients 
Fig. ...
1 10 100 
0 
clients 
Fig. 3.2: Server network traffic 
1 10 100 
20 
10 
0 
clients 
Fig. 3.4: Cache network traffic 
8 
...
Don’t build intelligent servers, 
because scaling them is expensive. 
Build servers that 
enable clients to be intelligent...
By offering a much simpler interface, 
DBpedia can be available like all sites. 
This lets us build Web applications 
on t...
Live DBpedia querying 
with high availability 
Ruben Verborgh
Live DBpedia querying with high availability
Nächste SlideShare
Wird geladen in …5
×

von

Live DBpedia querying with high availability Slide 1 Live DBpedia querying with high availability Slide 2 Live DBpedia querying with high availability Slide 3 Live DBpedia querying with high availability Slide 4 Live DBpedia querying with high availability Slide 5 Live DBpedia querying with high availability Slide 6 Live DBpedia querying with high availability Slide 7 Live DBpedia querying with high availability Slide 8 Live DBpedia querying with high availability Slide 9 Live DBpedia querying with high availability Slide 10 Live DBpedia querying with high availability Slide 11 Live DBpedia querying with high availability Slide 12 Live DBpedia querying with high availability Slide 13 Live DBpedia querying with high availability Slide 14 Live DBpedia querying with high availability Slide 15 Live DBpedia querying with high availability Slide 16 Live DBpedia querying with high availability Slide 17 Live DBpedia querying with high availability Slide 18 Live DBpedia querying with high availability Slide 19 Live DBpedia querying with high availability Slide 20
Nächste SlideShare
Initial Usage Analysis of DBpedia's Triple Pattern Fragments
Weiter

3 Gefällt mir

Teilen

Live DBpedia querying with high availability

Slides from talk at the DBpedia Community Meeting in Leipzig, 2014

Ähnliche Bücher

Kostenlos mit einer 30-tägigen Testversion von Scribd

Alle anzeigen

Live DBpedia querying with high availability

  1. 1. Live DBpedia querying with high availability Ruben Verborgh
  2. 2. “If DBpedia goes down, nobody complains. If the BBC Linked Data Platform goes down, that’s a problem for live applications.” Don’t we want live applications on top of DBpedia? It’s a vicious cycle: no apps because downtime, downtime acceptable because no apps.
  3. 3. Despite all traffic it receives, DBpedia has an uptime of around 95%, making it one of the more reliable endpoints. DBpedia is unavailable for 1.5 days each month.
  4. 4. Public endpoints like DBpedia are hosted voluntarily, as-is and free of charge. Since DBpedia is hosted for free, we should not complain too hard when it is unavailable.
  5. 5. The majority of the information on the Web is hosted voluntarily, as-is and free of charge. Wouldn’t we complain if that information was unavailable for 1.5 days a month?
  6. 6. There’s a difference! DBpedia offers a SPARQL interface, which is much more expensive than HTTP.
  7. 7. Exactly. If DBpedia offers information as-is and free of charge, why choose such an expensive interface? Why does it commit itself to such a strong engagement? (The BBC doesn’t do it!)
  8. 8. Why offer to answer complex queries if you cannot reliably answer simple ones?
  9. 9. SELECT * { ?s ?p ?o } LIMIT 1
  10. 10. What other interfaces to RDF are available? low server demand high server demand data dump SPARQL endpoint derefer-encing Triple Pattern Fragments
  11. 11. A triple pattern fragments interface is much less powerful than SPARQL. So also much less demanding, like other HTTP interfaces. Servers of triple pattern fragments have very high availability.
  12. 12. How do we handle complex queries? Clients execute them! SELECT ?person ?city WHERE { ?person a dbpedia-owl:Artist. dbpedia-owl:birthPlace ?city. ?city foaf:name "York"@en. } 2–3 seconds
  13. 13. data processing server
  14. 14. data processing server client
  15. 15. Server CPU usage remains low. 1 10 100 100 50 0 clients Fig. 3.3: Query timeouts 10 100 100 50 0 clients Fig. 3.5: Server processor usage per core 100 1 client 100 clients
  16. 16. 1 10 100 0 clients Fig. 3.2: Server network traffic 1 10 100 20 10 0 clients Fig. 3.4: Cache network traffic 8 6 Cache reuse becomes very high. 1 client 100 clients
  17. 17. Don’t build intelligent servers, because scaling them is expensive. Build servers that enable clients to be intelligent.
  18. 18. By offering a much simpler interface, DBpedia can be available like all sites. This lets us build Web applications on top of live DBpedia data. Let’s make simple things work reliably, then worry about the complex.
  19. 19. Live DBpedia querying with high availability Ruben Verborgh
  • qbu

    Jul. 24, 2015
  • steffenstaab

    Sep. 4, 2014
  • dannyeuu

    Sep. 3, 2014

Slides from talk at the DBpedia Community Meeting in Leipzig, 2014

Aufrufe

Aufrufe insgesamt

2.750

Auf Slideshare

0

Aus Einbettungen

0

Anzahl der Einbettungen

259

Befehle

Downloads

0

Geteilt

0

Kommentare

0

Likes

3

×