* [#configure　Bigdata　Configuration]

* [#load Load performance] 
    * [#allieload Allie upload]
    * [#pdbjload PDBJ upload]
    * [#uniprotload Uniprot upload]
    * [#ddbjload DDBJ upload]
* [#Sparql  Sparql query performance] 
    * [#alliequery Allie query performance]
    * [#pdbjquery PDBJ query performance]
    * [#uniprotquery Uniprot query performance]
    * [#ddbjquery DDBJ query performance]


=== Bigdata Configuration === #configure

The journal in Bigdata (please refer to [http://sourceforge.net/apps/mediawiki/bigdata/index.php?title=StandaloneGuide] for details.)

The WORM (Write-Once, Read-Many) is the traditional log-structured append only journal. It was designed for very fast write rates and is used to buffer writes for scale-out. This is a good choice for immortal databases where people want access to ALL history. Scaling is to several billions of triples. 

The RW store (Read-Write) supports recycling of allocation slots on the backing file. It may be used as a time-bounded version of an immortal database where history is aged off of the database over time. This is a good choice for standalone workloads where updates are continuously arriving and older database states may be released. The RW store is also less sensitive to data skew because it can reuse B+Tree node and leaf revisions within a commit group on large data set loads. Scaling should be better than the WORM for standalone and could reach to 10B+ triples. The default property file is attachment:RWStore.properties.


=== Load Performance === #load

Approach 1:

 Upload data from Bigdata sparql point(NanoSparqlServer). Post the data every 10000 lines. Please refer to attachment:upload.pl for details. 

Approach 2:

 Upload with com.bigdata.rdf.store.DataLoader tools and RW store default parameter.

And test the situation when adding GC in JVM. 
 
{{{
-Xmx55G -Xms30G -XX:+UseG1GC -XX:+TieredCompilation? -XX:+HeapDumpOnOutOfMemoryError
}}}

Approach 3:

We modified the following two important parameters(In the rest test we use this configure in default):
{{{
com.bigdata.btree.writeRetentionQueue.capacity=500000
com.bigdata.rdf.sail.BigdataSail.bufferCapacity=1000000
}}}

Approach 4: Split the file into 12 small files.

=== Allie upload === #allieload 
 
Approach 1: 26hours 

Approach 2: 5.89hours 
when Setting JVM GC : 6.75hours 

Approach 3: 2.61 hours

Approach 4: 1.03 hours  

=== PDBJ upload === #pdbjload 


'''Result:''' 8.95 hours

=== Uniprot upload === #uniprotload 

=== DDBJ upload === #ddbjload  


=== Sparql query performance === #Sparql

=== Allie query performance === #alliequery 

=== PDBJ query performance === #pdbjquery 

=== Uniprot query performance === #uniprotquery 

=== DDBJ query performance === #ddbjquery