Davart execution slow where ODP.net has no issues

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for Oracle
Post Reply
smackey
Posts: 3
Joined: Thu 08 Mar 2012 19:01

Davart execution slow where ODP.net has no issues

Post by smackey » Thu 08 Mar 2012 19:20

I am finding that if I call to a stored procedure returning a cursor that contains 14 columns (of which none are blobs/clobs) it is taking around 40 + mins to execute, but if I use ODP.net it executes in a little over 1 min.

I have executed the SQL in SQL Developer and it takes around 40 to 60 seconds to return all the data.

Is there a setting I need to change to get the Devart dll to perform better?

Code samples can be provided via email.

Thank you,
Shawn

Shalex
Devart Team
Posts: 8088
Joined: Thu 14 Aug 2008 12:44

Post by Shalex » Mon 12 Mar 2012 09:11

Could you please send us via our contact form a small test project with the corresponding DDL/DML script so that we can reproduce the performance issue in our environment? We will investigate it and notify you about the results.

smackey
Posts: 3
Joined: Thu 08 Mar 2012 19:01

Status

Post by smackey » Thu 22 Mar 2012 21:00

Are there any updates to this?

Shalex
Devart Team
Posts: 8088
Joined: Thu 14 Aug 2008 12:44

Post by Shalex » Fri 23 Mar 2012 15:18

We have answered you by e-mail.

smackey
Posts: 3
Joined: Thu 08 Mar 2012 19:01

Post by smackey » Fri 30 Mar 2012 18:31

The suggested alter session statement didn't change the timings on our runs. We ran a trace on the oracle side and didn't see ODP sending any hidden statements. Are there any additional suggestions before we provide the full trace and any additional info you need.

Shalex
Devart Team
Posts: 8088
Joined: Thu 14 Aug 2008 12:44

Post by Shalex » Mon 02 Apr 2012 12:19

Please try the following:
1) use ALL_ROWS instead of FIRST_ROWS_1 in the alter session statement;
2) localize the line of code which takes a lot of time to execute (it can be cmd.ExecuteReader(), reader.GetXXX(), etc).

If this doesn't help, please send us the DDL/DML script to fill your schema (or code which will fill it) so that we can reproduce the timing issue in our environment.

Post Reply