Difference between revisions of "LUBM"

From Blazegraph
Jump to: navigation, search
(Created page with 'The following instructions will let you run the LUBM benchmark against an embedded bigdata database. The NanoSparqlServer is used to answer SPARQL queries. It "knows" about big…')
 
Line 1: Line 1:
 
The following instructions will let you run the LUBM benchmark against an embedded bigdata database.
 
The following instructions will let you run the LUBM benchmark against an embedded bigdata database.
  
The NanoSparqlServer is used to answer SPARQL queries.  It "knows" about bigdata's MVCC semantics (multi-version concurrency control) and will issue queries to a read-only connection reading from the last commit time on the database and may have somewhat better performance or concurrency as a result.  
+
The NanoSparqlServer is used to answer SPARQL queries.  It "knows" about bigdata's MVCC semantics (multi-version concurrency control) and will issue queries to a read-only connection reading from the last commit time on the database and may have somewhat better performance or concurrency as a result. You can more or less follow the same instructions if you want to run against a bigdata federation, but you will have to have the federation up and running already and you will have to use the bulk data loader for the federation to get the data into the database.
 
+
You can more or less follow the same instructions if you want to run against a bigdata federation, but you will have to have the federation up and running already and you will have to use the bulk data loader for the federation to get the data into the database.
+
  
 
<pre>
 
<pre>

Revision as of 17:04, 15 June 2010

The following instructions will let you run the LUBM benchmark against an embedded bigdata database.

The NanoSparqlServer is used to answer SPARQL queries. It "knows" about bigdata's MVCC semantics (multi-version concurrency control) and will issue queries to a read-only connection reading from the last commit time on the database and may have somewhat better performance or concurrency as a result. You can more or less follow the same instructions if you want to run against a bigdata federation, but you will have to have the federation up and running already and you will have to use the bulk data loader for the federation to get the data into the database.

# check out the trunk:
svn checkout ....

# build bigdata
ant clean bundleJar

# Switch to the lubm package.
cd bigdata-lubm

##
# Edit build.properties
##

# generate the LUBM data set per the build.properties file.
ant run-generator

# load an LUBM data set into bigdata per the build.properties file.
ant run-load

# start an http sparql endpoint for that bigdata database instance.
ant start-nano-server

# run the lubm queries.
ant run-query