Description
What PostProcessBenchmarkSpec supposed to do is testing performance of methods on PostProcess.
Currently, this spec does following on setup phase.
- delete and re-create test Service
- delete and re-create test Label
- insert test data into HBase
also to run PostProcess`s method, it actually fetch inserted data from setup phase.
I suggest not create test Label and insert test data entirely.
instead we can create QueryRequest, QueryResult, QueryRequestWithResult classes without actually store test data.
I think by using mocked edges
- we can run this test without need for DBMS and HBase so we can concentrate on PostProcess logic`s performance only.
- more flexible and fast test can be possible with regard to number of edges in QueryResult.
In general, I think there should be no dependency on RDBMS + HBase for benchmark specs.