Thanks,
Santosh
http://www.ontruenorth.com
Follow us on Twitter: http://twitter.com/truenorth_buzz
Thanks,
Santosh
Rahul Babbar
) Why should the performance of the query reduce when you select the last set of records, since the query that you are executing is the same, only that the rownum values are different.(0.1-2 to 120 secs) is too much of a difference for the SAME query being fired.
Paul Sturrock wrote:
Its not the same query. Its repeated simmilar queries (see the SQL generated).
Rahul Babbar
Thanks,
Santosh
Santosh Ramachandrula wrote:Rahul,
For your questions 1 & 2 please see similar issue at http://forum.springsource.org/archive/index.php/t-61016.html
Rahul Babbar
Rahul Babbar wrote:
Santosh Ramachandrula wrote:Rahul,
For your questions 1 & 2 please see similar issue at http://forum.springsource.org/archive/index.php/t-61016.html
Thanks for the above link, it indeed is the same issue.
However, the discussion(in the link) also does not seem to give a proper explanation as to why the query should be slower for the last set of records...
It could be a bug in some version of Oracle 10g or.....(well, i cant see any other reason...)
If you look at that query closely, you'll notice that it incorporates a top-N query (get the first :MAX_ROW_TO_FETCH rows from your query) and hence benefits from the top-N query optimization I just described. Further, it returns over the network to the client only the specific rows of interest—it removes any leading rows from the result set that are not of interest.
Rahul Babbar
Hey cool! They got a blimp! But I have a tiny ad:
Clean our rivers and oceans from home
https://www.kickstarter.com/projects/paulwheaton/willow-feeders
|