Hi G,
I saw similar behaviors in some of my lightweight app, which also uses
sqlite and rocket. I need not solve that problem at that time (it was
really a little app for a small group). But I can provide some
information to you this time.
When you try to isolate the sqlite, "using no auth and randomly
generating data" are not enough. You would better completely take out
this line:
db = DAL('sqlite://storage.sqlite')
that means completely avoid db definition and db opening. That is
because, in web2py, even a sqlite db open attempt will open the db in
exclusive mode, hence blocking other requests to the same app. (That
was true, I don't know whether that was changed since then. Massimo
can confirm that.)
Regards,
Ray
On Aug 25, 6:37 am, G <glenn.calt...@gmail.com> wrote:
> Thank you for the suggestion. I made a test application that used no
> database accesses (no auth and randomly generated data). It showed the
> same behavior, so I do not think it is the culprit. In addition, since
> the application is monitor only, the real application only reads from
> the database, which I hope would not impose a transaction lock.
>
> G
>
> On Aug 24, 3:20 pm, ron_m <ron.mco...@gmail.com> wrote:
>
> > You also need to consider the database type used by the application for the
> > model. The SQLite database has a transaction lock which will cause the
> > application to look like it is single threaded if the database is held in a
> > transaction pending state while the background work is performed.
