Note: You need an SVG-enabled browser to view the following pages.

Preliminaries

Systems

Experiments were run on systems with characteristics listed below:

Datasets

Experiments are based on synthetics datasets. Datasets are named Dⁱ_j, where i is the input factor used to generate XMark data, and j is the number of triples, as a ratio of XML nodes. For instance, D¹⁰_1/3 contains 16M XML nodes, and roughly 5M triples. The sizes of relative data are listed in the table below:

Workloads

Charts

• XML||RDF: Independent executions (detail)
• XML->RDF: Bind XML, then RDF (detail)
• RDF->XML-URI: Bind RDF, then push URIs (detail)
• RDF->XML-URI-Pr: Bind RDF, prune, then push URIs (detail)
• RDF->XML-XPath: Bind RDF, then push XPaths (detail)
• RDF->XML-XPath-Pr: Bind RDF, prune, then push XPaths (detail)

The remaining, hatch-patterned, bars are the respective tuple-at-a-time counterparts of the RDF-to-XML approach above with and without pruning.

• Colored bars indicate execution time averaged over 3 runs.
• Bars with negative values indicate the data was missing (most likely the timeout for the whole set of strategies expired, in some fewer case this indicates a crash).
• Columns labeled ‘—’ must be ignored.
• Cardinalities of the queries are indicated between parenthesis under each serie. ‘-1′ means none of the strategies completed with the allocated 5 minutes.

Strategies side-by-side

Scalability

Recent results

We recently experimented with a new set of strategies involving materialization.

• XML||RDF: Independent executions (detail)
• XML->RDF-Data: Bind XML, then push to RDF data (detail)
• RDF->XML-URI-Data: Bind RDF, then push to XML data (detail)
• RDF->XML-URI-Data-Pr: Bind RDF, prune, then push to XML data (detail)

Strategies side-by-side

Scalability