cfquery with maxrows = faster processing ?

Ask a Question related to Coldfusion Database Access, Design and Development.

  1. #1

    Default Re: cfquery with maxrows = faster processing ?

    Yes, there is an increase in speed, as returning 10 rows is less work than
    returning 50, but that may not be the whole story. Most of a query's work is
    done in getting the result set from the database in the first place. I presume
    that Coldfusion would have been designed in such a way that it caches the full
    result set in a buffer, even though it only returns a maxrows of 10. If so,
    then the overall increase in speed from using maxrows will not be significant.
    In any case, I even wonder whether it's any use thinking of speed gains for row
    numbers as small as 50.



    BKBK Guest

  2. Similar Questions and Discussions

    1. cfquery with maxrows supposed to be faster?
      The query speed will not be affected. The page will load more quickly though, if you are displaying only 10 rows of data rather than 50. How long...
    2. cfoutput cfquery "group processing" error
      I am attempting to write data to an html table from three different Access tables. I have three (3) queries in the cftransaction, each later query...
    3. Using Maxrows with Nested Output
      This seems so simple but how does MAXROWS work with nested queries that are grouped? If you apply it at the top level it limits the number of...
    4. CFQUERY and maxrows attribute
      ok, maybe I'm on some bad crack today, but I recall that the maxrows attribute of cfquery works AFTER the resultset is returned to CF from the DB. ...
    5. CFGRID ? maxRows
      I agree with ArtNirvana. If you have maxRows then is reasonable to have page navigation and also you can think about record locator based on sort...
  3. #2

    Default Re: cfquery with maxrows = faster processing ?

    BKBK wrote:
    > done in getting the result set from the database in the first place. I presume
    > that Coldfusion would have been designed in such a way that it caches the full
    > result set in a buffer, even though it only returns a maxrows of 10. If so,
    depends on the db & db driver. in something like sql server when the
    resultset reaches the maxrows value processing stops on the server.
    something like access probably gets the whole resultset & that is truncated.
    PaulH *TMM* Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139