Johann, there were no views in the example.
On Tue, Feb 7, 2012 at 6:35 AM, Johann Spies <johann.sp...@gmail.com> wrote: > On 7 February 2012 09:27, Bruce Wade <bruce.w...@gmail.com> wrote: >> >> You are using a for loop with 100000 inserts it is the for loop holding >> you up not web2py. Plus who in their right mind would code something like >> that in production > > > I understood him differently: the result of query after the 100k rows were > loaded took 5-6s to appear in the view. > > I just did a test at a database I am working with daily: It is a complex > database and the table I am querying has 326543 records with several links > to other tables. Using SQLFORM.grid to show the contents of 6 fields took > 13 seconds for the first page to show up in the view when using the server > which serves the page through apache over the network. On my laptop > (localhost:8000) the same query with the same database content took 6 > seconds to show up.. That is not particularly fast. BUT: subsequent > queries took less than a second in both cases even when I used a different > browser. So it cannot be the browser cache that made the difference. > > So the lesson for the day: If you want to test responses, don't just take > one or two reactions as the final answer. > > Regards > Johann > -- > Because experiencing your loyal love is better than life itself, > my lips will praise you. (Psalm 63:3) >
