Let's take a good chunk of the app dealing with the data before doing another
fetch bit of the equation.
Instead of using the data grid, run the same query with F5. That way there's no
worrying about the grid doing its work to display the data before getting the
next batch of data.
Also, what's your SQL Array Fetch size set to in Preferences > Database >
Advanced?
50 won't be very friendly if you're going to grab 100k rows, go up to the max
we allow, 200. I'm guessing the grid, ctrl + PgDn will go a bit faster this
time.
Jeff
-----Original Message-----
From: Lothar Flatz [mailto:l.flatz@xxxxxxxxxx] ;
Sent: Thursday, March 09, 2017 10:07 AM
To: Jeff Smith <jeff.d.smith@xxxxxxxxxx>
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Fetch speed in SQL Developer
Hi Jeff,
i know an application that fetches 80.000 - 100.000 rows. (Yeah, that does not
make sense, it is OLTP).
SQL trace show that the db is waiting on sql net message from client between
fetches.
(Don't anybody tell me that is an idle wait event, it is not in this
case.) I suspect that the application is processing the rows and the db is
waiting for it.
Now the application vendor has told my customer to fetch 100.000 rows in sql
developer as for a test and indeed my client is waiting around 20 seconds,
fetching all rows using cntrl + PageDown.
This seems actually too long. However I am not sure if that is a valid test for
the network transfer rate or SQL Developer is taking a time toll fetching the
rows.
Therefore I am asking. Tests on my laptop suggest it is really the network
transfer that takes the time.
Since this is a question that might concern others as well I included the list.
Regards
Lothar
--
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
