Closed Ask-sola closed 1 year ago
I don't think we save the parameter - runtime combinations because it would result in excess disk IO. @GLaDAP knows more about the internals of the benchmark, so adding him to cc.
Okay, thank you for your answer. I have added code logging in the implementation section myself
After I finished executing the benchmark, I attempted to view the time spent on each query, but the resulting file contained two that were not what I needed:
”LDBC SNB results. json“ contains aggregated information of different query results, and I am not aware of the results of each query.
”LDBC-SNB results_ Log. csv "displays the time used for each query, but the reference information it provides still does not include the content of a specific query, it only includes the statement type of the query.
If I want to know which query parameter and how long does the query statement take to run, how should I proceed?