Hi Lekshmi, Basically, I think you just need to add some log information inside Prepare <https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/prepare/Prepare.java> . Possibly it suffices to replace calls to timingTracer <https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/prepare/Prepare.java#L96> with calls to an actual logger. If you need more help I will try to provide a small patch.
Best, Stamatis Στις Πέμ, 27 Δεκ 2018 στις 1:09 μ.μ., ο/η Lekshmi <[email protected]> έγραψε: > Hi Stamatis, > I was working on getting the planning/ execution time of TPC-H > queries using calcite TPC-H test cases. But I got significantly large time > than PostgreSQL. When I analyses the code, I suppose that, It took the > time to generate the TPC-H data and execute the queries on that. I would > like to compare the performance of Calcite with PostgreSQL on executing the > TPC-H queries. For that, I would like to get at least the planning time of > TPC-H queires on Calcite. Can you please help me with any points to get it? > Thanks and Regards > > Lekshmi B.G > Email: [email protected] > > > > > On Sat, Dec 1, 2018 at 10:28 AM Stamatis Zampetakis <[email protected]> > wrote: > > > Hi Lekshmi, > > > > I don't think that you can obtain this information easily. The current > > implementation of explain does not seem to provide this information. > > If you are willing to dig in a bit into the code you might find useful > the > > following entry points regarding the timing of queries: > CalciteTimingTracer > > < > > > https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/util/trace/CalciteTimingTracer.java > > > > > , CalciteTrace > > < > > > https://github.com/apache/calcite/blob/439ca73b8a335213b5f2764514b14e17c9d3c216/core/src/main/java/org/apache/calcite/util/trace/CalciteTrace.java#L103 > > > > > . > > > > Best, > > Stamatis > > > > Στις Παρ, 30 Νοε 2018 στις 11:33 μ.μ., ο/η Lekshmi < > [email protected]> > > έγραψε: > > > > > Hi, > > > I was comparing the performance of PostgreSQL and Calcite. I can > > collect > > > the planning and execution time from PostgreSQL using "explain analyze" > > but > > > from calcite I didnt get all the information using "explain all > > > attributes". I would like to know how can we collect the execution time > > and > > > planning time of a query from calcite..It would be great, if anyone > help > > > me.. > > > > > > Thanks and Regards > > > > > > Lekshmi B.G > > > Email: [email protected] > > > > > >
