# Dremio slower than SQL Developer?

**URL:** <https://community.dremio.com/t/dremio-slower-than-sql-developer/2817>\
**Category:** Uncategorized\
**Created:** [February 21, 2019, 11:53am UTC](https://community.dremio.com/t/dremio-slower-than-sql-developer/2817 "2019-02-21T11:53:44Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![h4nneke](https://avatars.discourse-cdn.com/v4/letter/h/ecb155/32.png) [@h4nneke](https://community.dremio.com/u/h4nneke)\
**Post date:** [February 21, 2019, 11:53am UTC](https://community.dremio.com/t/dremio-slower-than-sql-developer/2817/1 "2019-02-21T11:53:44Z")

</div>

I translated my query on my Oracle DB to Dremio expecting that it would be faster (or at least as fast), but in SQL developer it takes 33 seconds and in Dremio 3 minutes. Wat could be the problem?

---

<div class="post-metadata">

**Author:** ![ben](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/ben/32/1367_2.png) [@ben](https://community.dremio.com/u/ben)\
**Post date:** [February 21, 2019, 3:32pm UTC](https://community.dremio.com/t/dremio-slower-than-sql-developer/2817/2 "2019-02-21T15:32:40Z")

</div>

Hi @h4nneke,

Can you provide a profile for the query in question? This would help use understand where the time is spent.

> **[How To Share A Query Profile](https://www.dremio.com/tutorials/share-query-profile-dremio/)**
>
> Tutorial explaining how to share a query profile in Dremio.

---

<div class="post-metadata">

**Author:** ![h4nneke](https://avatars.discourse-cdn.com/v4/letter/h/ecb155/32.png) [@h4nneke](https://community.dremio.com/u/h4nneke)\
**Post date:** [February 21, 2019, 4:43pm UTC](https://community.dremio.com/t/dremio-slower-than-sql-developer/2817/3 "2019-02-21T16:43:22Z")

</div>

This is the query profile.

[10c68e90-246a-4725-8060-79bab0a88995.zip](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/e/eae4d2e81578b6037e6a3da5b60abb387499cfdc.zip) (98.7 KB)

---

<div class="post-metadata">

**Author:** ![ben](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/ben/32/1367_2.png) [@ben](https://community.dremio.com/u/ben)\
**Post date:** [February 21, 2019, 9:12pm UTC](https://community.dremio.com/t/dremio-slower-than-sql-developer/2817/4 "2019-02-21T21:12:56Z")

</div>

@h4nneke,

Rather than pushing the whole query down into Oracle, Dremio is breaking it up into 5 separate pushdowns and doing some of the joins itself. The majority of the those 3+ minutes is spent in 2 particular pushdown which can be seen at 08-05 and 07-03 of the “Final Physical Plan” of the “Planning” tab. Why those particular queries would take more time is a bit of mystery. You can cut and paste them from the query profile and run them in SQL Developer to see what the times are there.

As for why Dremio doesn’t push down the whole query, I will have to take a deeper look and get back to you.

---

<div class="post-metadata">

**Author:** ![ben](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/ben/32/1367_2.png) [@ben](https://community.dremio.com/u/ben)\
**Post date:** [February 26, 2019, 3:59am UTC](https://community.dremio.com/t/dremio-slower-than-sql-developer/2817/5 "2019-02-26T03:59:11Z")

</div>

@h4nneke,

To get a more detailed understanding of why Dremio does not pushdown the whole query, you could stop the server, add the following logger to `logback.xml`, resart:

```
<logger name=“com.dremio.exec.store.jdbc”>
   <level value=“${dremio.log.level:-debug}“/>
 </logger>

```

Then, rerun the query and attach `server.log` here. This will give more verbose messaging for the JDBC plugin.

If you try this, you will want to _remove the logger when your done_ to avoid spamming your `server.log` with debug messages.

---

<div class="post-metadata">

**Author:** ![kelly](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/kelly/32/11_2.png) [@kelly](https://community.dremio.com/u/kelly)\
**Post date:** [February 26, 2019, 4:34am UTC](https://community.dremio.com/t/dremio-slower-than-sql-developer/2817/6 "2019-02-26T04:34:08Z")

</div>

You can also try creating Data Reflections to see if that is faster than a push down.

Here are the docs: [https://docs.dremio.com/acceleration/reflections.html](https://docs.dremio.com/acceleration/reflections.html)

And here’s a tutorial: [https://www.dremio.com/tutorials/getting-started-with-data-reflections/](https://www.dremio.com/tutorials/getting-started-with-data-reflections/)

Also, there’s a new course on [university.dremio.com](http://university.dremio.com) for Data Reflections.

---

<div class="post-metadata">

**Author:** ![unni](https://avatars.discourse-cdn.com/v4/letter/u/96bed5/32.png) [@unni](https://community.dremio.com/u/unni)\
**Post date:** [May 15, 2020, 5:51pm UTC](https://community.dremio.com/t/dremio-slower-than-sql-developer/2817/7 "2020-05-15T17:51:59Z")

</div>

@kelly@ben Any learnings from this issue?

---

<div class="post-metadata">

**Author:** ![ben](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/ben/32/1367_2.png) [@ben](https://community.dremio.com/u/ben)\
**Post date:** [May 15, 2020, 6:15pm UTC](https://community.dremio.com/t/dremio-slower-than-sql-developer/2817/8 "2020-05-15T18:15:14Z")

</div>

@unni I cannot make any specific claims unless I see a Dremio profile and the same job executed in SQL Developer. SQL Developer probably has a multithreaded read from the RDBMS while Dremio is single threaded, so that may cause the difference in performance.
