The difference between the two is that in former case the output returned
by the DB is normalized (each record is a Row object) while in the
executesql case the output is not normalized (each record is a tuple
containing data in the database specific representation). It does take time
to loops
I don't care about ORM performance which is worse both in term of bare
performance and in development speed, but using large databases and doing
profiling I find that most of the time that is "spent on DB IO" is ispent
inside python code unless executesql is used. There is still a lot of room
for
It really depends on what one compares.
I do not think we ever published benchmarks claiming web2py is faster than
other frameworks. If one want speed raw WSGI (perhaps with gunicorn or
gevent) without templates and without databases beats every framework. The
more a framework does, the slower
I seem to remember vividly seeing a benchmark about 4 years ago that showed
that web2py was indeed the fastest.
Either that benchmark was misleading, or things have changed.
In either case, it would still remain important to explain to the public
the reasons for the trade-offs that were chosen. I
Web2py can not be the fastest, but it is the most simple and functional for
everyone.
Ovidio Marinho Falcao Neto
ITJP.NET.BR
ovidio...@gmail.com
83 8826 9088 - Oi
83 9336 3782 - Claro
Brasil
201
Because I think it is pointless for various reasons:
1) I am biased and people outside the community would not trust it
2) Code changes so it would become obsolete quick
3) One can produce benchmarks to produce almost any result one wants
4) People who are concerned about 2x factors in speed are n
Massimo, how about you writing an article about this subject and share with us?
So, this could be spread.
On Thu, Jul 11, 2013 at 2:12 PM, Massimo Di Pierro
wrote:
> I agree. I will do.
>
> On Thursday, 11 July 2013 11:51:39 UTC-5, Arnon Marcus wrote:
>>
>> I see.
>> In that case, I think it wou
I agree. I will do.
On Thursday, 11 July 2013 11:51:39 UTC-5, Arnon Marcus wrote:
>
> I see.
> In that case, I think it would be advisable to note that in presentations,
> as peope might get the wrong impression...
>
> On Thursday, July 11, 2013, Massimo Di Pierro
> >
> wrote:
> > It is true bu
I see.
In that case, I think it would be advisable to note that in presentations,
as peope might get the wrong impression...
On Thursday, July 11, 2013, Massimo Di Pierro
wrote:
> It is true but not an issue. Django is faster only in hello world
examples because does not perform as many header va
9 matches
Mail list logo
