HI Marc, Any chance you could upgrade to Drill 1.17? I know there were significant improvements between versions. I'd be curious to see if that makes a difference. --C
> On May 14, 2020, at 9:39 AM, Marc Sole Fonte <[email protected]> wrote: > > Hello, > > I have seen an answer but I am not able to answer it directly. The Drill > version I am using is 1.16.0. > > The transcript for the images is more or less the following one: > > Planning Queued Execution Total > 0.219 sec 0.070 sec 15.166 sec 15.455 sec > 0.186 sec 0.036 sec 16.944 sec 17.166 sec > > If you need more data, feel free to ask for it. Thank you for your help. > > Marc > > > On Thu, 2020-05-14 at 12:50 +0200, Marc Solé wrote: >> Hello, >> >> First of all, I hope you and your families are all safe and healthy. Also, >> thank you in advance for your support. >> >> I have a problem with Apache Drill conected to CockroachDB (PostgreSQL) >> using the RDBMS Storage Plugin. It works, but it is extremely slow. My >> experience with Drill has showed me a lot of scenarios where the first query >> is slow, due to planification, but the next ones are acceptable, assuming >> the time consumed by the man in the middle. However, this does not seem >> normal at all. >> >> Running a small and simple query like this one: SELECT * FROM >> db_scott_centria.public.centria_raw LIMIT 1, execution times are completely >> over the limit. It takes about 15 seconds of Execution Time. Both Apache >> Drill and the database are in the same network, and a query from terminal >> from the same takes only some milliseconds. Where is the problem? What can I >> do to improve that time? >> >> Here are some pictures with examples: >> >> >> >> >> >> Thank you very much for your help, I hope you can help me. >> >> Marc
