Somewhere in your code you are probably fetching all the rows. Look at all your queries and see whether you can paginate results somehow (using limitby). Look at IS_IN_DB validators etc which create drop down boxes and consider using sub-sets of data to populate them, or replace with autocomplete.
Without seeing any code, it is difficult to be specific. Regards, D On Mar 9, 5:52 pm, Philip <philip.el...@gmail.com> wrote: > I am having an issue with an application. Page load times are 20+ > seconds. This is true for all pages, even in admin functions (as soon > you select the application in question). It appears to be a database > problem, since the problem appeared after adding about 15,000 records > to an application that was working well with far fewer (probably > ~2000). I am using sqlite as the backend and running an internal > application on a windows server that is also used as a fileshare. The > applications has 8 tables, 4 of 5 which have over 2000 records, the > largest is about 6000 records. The tables are quite small, so the > total db.db file size is still just over 1MB (worked great when it was > only 250kB), despite the number of records. Problem occurs both when > running locally installed on my machine or over the network to the > server-hosted version. In both cases, only one user was using the > application. > > I have tried migrate=false and compiling the app as the web2py book > suggests - no noticable improvement. > > Looking online for performance and scalability of sqlite, it seems > that I am still well under any size that would cause an sqlite > performance issue. > > Does anyone know of any common root causes of performance problems > like that? > > Thanks
