バージョン 38 から バージョン 39 における更新: survey
- 更新日時:
- 2012/07/05 10:54:58 (12 年 前)
凡例:
- 変更なし
- 追加
- 削除
- 変更
-
survey
v38 v39 20 20 We present an evaluation of native triple stores on biological data. Compared with the data in other areas biological data is typically huge. Therefore the performance of bulk loading and querying are essential to decide whether a triple store can be applied into the biological field. Here we test five native triple stores Virtuoso, OwlimSE, Mulgara, 4store, and Bigdata with five biological dataset, which ranging from tens of millions to eight billions. We present their load times and query cost. 21 21 22 For each database we provide several results by adjusting their parameters, which could influence the performance importantly. However These parameters could perform differently with different hardware and software platforms, and even with different data set. It is difficult to test all the performance by adjusting and combining all the parameters for every data set because the importing of our data set, such as uniprot and DDBJ, takes over two days or more. Therefore we do not guarantee what we provide is the best performance of each database although we try to find out the best performance for each triple store.22 For each database we provide several results by adjusting their parameters, which could influence the performance importantly. However These parameters could perform differently with different hardware and software platforms, and even with different data set. It is difficult to test all the cases by adjusting and combining all the parameters for every data set because the importing of our data set, such as uniprot and DDBJ, may take over two days or several weeks. Therefore we do not guarantee what we provide is the best performance of each database although we try to find out the best performance for each triple store. 23 23 24 24 '''4store''' … … 87 87 === Approach === #approach 88 88 89 We evaluated the data in every Sparql end point at least twice to make it sure that there is no much difference between two test values:|2nd-1st|/max(2nd,1st)<0.1 .89 We evaluated the data in every Sparql end point at least twice to make it sure that there is no much difference between two test values:|2nd-1st|/max(2nd,1st)<0.1(now we took the first value because some loading is still in test ). 90 90 91 91 We did the query evaluation by executing the whole query mix (composed of the query sequence) five times in every Sparql endpoint, remove the highest one and then get the average time cost of other four queries. We report the five detailed time cost in every database section and the average cost in the summary section.
