Enabling ne-grained HTTP caching of SPARQL query results thumbnail
Pause
Mute
Subtitles
Playback speed
0.25
0.5
0.75
1
1.25
1.5
1.75
2
Full screen

Enabling ne-grained HTTP caching of SPARQL query results

Published on Nov 25, 20113522 Views

As SPARQL endpoints are increasingly used to serve linked data, their ability to scale becomes crucial. Although much work has been done to improve query evaluation, little has been done to take advan

Related categories

Chapter list

Enabling fine-grained HTTP caching of SPARQL query results00:00
Overview00:10
Why HTTP caching?01:04
Caching Motivation01:36
Framework - 102:49
Framework - 203:20
Example03:35
Fine-grained?04:24
Example Query 104:46
Example Update04:57
Example Query 205:07
Basic Idea05:16
Related Work05:35
What is ‘relevant data’? - 106:26
What is ‘relevant data’? - 206:43
What is ‘relevant data’? - 307:01
How can we recognize “relevant data”?07:31
Search trees in semantic web systems07:36
Search Tree Augmentation08:39
mtime update algorithm09:52
B+ Trees - 110:39
B+ Trees - 210:56
B+ Trees - 311:06
B+ Trees - 411:07
B+ Trees - 511:11
B+ Trees - 611:18
B+ Trees - 711:24
B+ Trees - 811:25
B+ Trees - 911:37
B+ Trees - 1011:42
B+ Trees - 1111:44
B+ Trees - 1211:51
Choices...11:59
Query algorithm12:28
Evaluation13:31
Read-only Throughput14:28
Read-write Throughput15:18
Cost of Caching Code15:52
Comparison with previous work16:41
Summary18:13
Future Work18:44
Thank You20:12