Thanks for the suggestion. I started a web2py session from the command
line, and ran a simple DAL select from there.
python web2py.py -M -S myapplication
result =
db2(db2.soe_tdb.pointnumber>0).select(db2.soe_tdb.ALL,limitby=(0,10))
print db2._timings
[("ALTER SESSION SET NLS_DATE_FORMAT =
If it was me, I'd eneable oracle events trace and look at the plans and
wait times for the two executions.
There are a few ways to do this, don't know of a web2py DAL specific one,
but look for
This article explains.
https://oracle-base.com/articles/misc/sql-trace-10046-trcsess-and-tkprof
Hi,
there should be something wrong going on.
As a first step, I'd write a simple query (i.e., select(db.table.ALL,
limit=(0,10)) using pydal (the database abstraction layer used in web2py)
and try to find out in which version has been introduced this performance
issue. If you don't find a
3 matches
Mail list logo