hich9n / cumulusrdf

Automatically exported from code.google.com/p/cumulusrdf
0 stars 0 forks source link

cumulusrdf-benchmark #52

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Work on cumulusrdf-benchmark module.

Pointer:
   * http://perf4j.codehaus.org/ 
      * Perf4J is a set of utilities for calculating and displaying performance statistics for Java code.
      * http://stackoverflow.com/questions/2158176/have-you-used-perf4j-to-collect-and-analyze-performance-metrics-in-java-app
* https://github.com/gladwig/exrunner 
      * A simple tool to run experiments in Java and record results in SQLite
* https://blog.codecentric.de/en/2014/01/automating-jmeter-tests-maven-jenkins/
      * Automating JMeter tests with Maven and Jenkins

Original issue reported on code.google.com by andreas.josef.wagner on 14 Apr 2014 at 3:23

GoogleCodeExporter commented 9 years ago
* http://jamonapi.sourceforge.net/
* http://code.google.com/p/javasimon/

Original comment by andreas.josef.wagner on 14 Apr 2014 at 3:38

GoogleCodeExporter commented 9 years ago
Java microbenchmark:

"A microbenchmark attempts to measure the performance of a "small" bit of code. 
These tests are typically in the sub-millisecond range. The code being tested 
usually performs no I/O, or else is a test of some single, specific I/O task.

Microbenchmarking is very different from profiling! When profiling, you work 
with an entire application, either in production or in an environment very 
painstakingly contrived to resemble production. Because of this, you get 
performance data that is, for lack of a better term, real. When you 
microbenchmark, you get a result that is essentially fictional, and you must be 
very careful about what conclusions you draw from it." 

=> https://code.google.com/p/caliper/

Original comment by andreas.josef.wagner on 14 Apr 2014 at 3:45

GoogleCodeExporter commented 9 years ago
-> Yongtoa.

Original comment by andreas.josef.wagner on 15 Apr 2014 at 3:52

GoogleCodeExporter commented 9 years ago
we should evaluate
1. write performance
2. read performance
based on BSBM, DBPedia benchmark or SP2 SPARQL.
10M, 100M and 1T triples for 10 - 20 queries

Baselines: 4store, Sesame, Jena

Original comment by mayong...@gmail.com on 14 May 2014 at 12:06

GoogleCodeExporter commented 9 years ago
Started work in r1329.

* Benchmark used: SP2 SPARQL benchmark
* Baselines: CumulusRDF v0.6.0, CumulusRDF v1.0.0, CumulusRDF v1.0.1, 
Sesame2Native

NOT YET FULLY DEBUGGED (THUS, NOT CODE IS NOT WORKING PROPERLY) ... COMMITTED 
ONLY TO HAVE VERSIONING.

Original comment by andreas.josef.wagner on 5 Jun 2014 at 11:38

GoogleCodeExporter commented 9 years ago
Benchmark module is working in r1422, but not fully functional.

Original comment by andreas.josef.wagner on 28 Jun 2014 at 2:45