Try to add lazy_tables=True to DAL. Like:
db = DAL('sqlite://storage.sqlite', migrate=False, lazy_tables=True)
Paolo
On Tuesday, January 15, 2013 10:06:03 AM UTC+1, Daniel Gonzalez wrote:
>
> No imports in the code-area profiled. Also, I am testing some requests,
> but the time I am measuring i
No imports in the code-area profiled. Also, I am testing some requests, but
the time I am measuring is the time spent in the code-area that I have
provided. That is, in the define tables code. The controllers are of course
making use of the table definitions later, but that is not what I am
mea
It will run only when called!
But if he is testing a form, the problem maybe there.
There are some imports?
--
It really runs these validators during table definition, and not just in
time when used? So its better to define this requires= ... in controller
where this is used?
David
Dne úterý, 15. ledna 2013 9:23:43 UTC+1 rochacbruno napsal(a):
>
>
> On Tue, Jan 15, 2013 at 6:20 AM, Daniel Gonzalez
>
>
Very few records (around 10). I am testing still.
On Tuesday, January 15, 2013 9:23:43 AM UTC+1, rochacbruno wrote:
>
>
> On Tue, Jan 15, 2013 at 6:20 AM, Daniel Gonzalez
>
> > wrote:
>
>> IS_NOT_IN_DB(db, '%s.email' % (web2py_user_table))
>
>
> If you too many records on user table, the above c
On Tue, Jan 15, 2013 at 6:20 AM, Daniel Gonzalez wrote:
> IS_NOT_IN_DB(db, '%s.email' % (web2py_user_table))
If you too many records on user table, the above code will take a long
time, because on every request it will "select email from auth_user"
--
Hi,
My db.py takes a long time to run (around 40 ms). This means that just the
overhead of db.py limits my throughput to 25 req/s (in a single process /
single thread configuration). This seems to me quite low.
I have tried to take a look at where the time is spent. I have seen the
following r
7 matches
Mail list logo
