Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • Finally! This is by far the clearest explanation. Your analogy makes a ton of sense. Thank you.
    – daveslab
    Commented Feb 16, 2012 at 21:03
  • oh,, thanks for the award ;)) just a side note, i guess Oracle might precache the data that will be fetched next, so d) is not really an issue
    – Aprillion
    Commented Feb 16, 2012 at 21:18
  • So what will be this typical throttle size, aka practical size of pipe?
    – Sumedh
    Commented Jan 10, 2013 at 11:55
  • @Sumedh too many variables, you need to do your own tuning for your project, en.wikipedia.org/wiki/Performance_tuning
    – Aprillion
    Commented Jan 21, 2013 at 13:23
  • Given that in most case, processing of results and fetching are synchronous, I am curious to know, between each fetching, is Oracle doing any work to prepare for subsequent fetches? If not, then it is simply like, 1st person only folds required number of papers that 3rd person ask for, and when 3rd person is cutting shape, 1st person just stand still without doing anything. Then apart from point 3 about TCP/IP throttling, setting a fetch size of 1000 is not going to be worse than 10. Is my understanding correct? Commented Nov 21, 2014 at 2:20