My experiments are all pretty old.  Too old to be useful.

Currently I have commercial websites using web2py and I don't need to do 
anything remarkable to make it faster.  I just used good design techniques 
and didn't do "premature optimization."  I'm now re-writing a Rails, site, 
a Java site, and an older web2py site into a combined site that will do all 
of the above.  My database is MySql and has about 50 tables, with 20 to 100 
columns in each.  My largest table has about 3M rows in it.  I expect 30M 
when I'm done.

I chose indexes carefully and I used "modules" (i.e. compiled python) for 
most of the model/controller details.  The beta site beats the pants off 
the sites it is replacing.  No pypy needed.  No cython either.

If you're looking at platform "benchmarks" to make a decision of what is 
fast enough, just don't do that.  The benchmarks I looked at turned out to 
be worse than useless in practice.  Most benchmarks pare down the task into 
something small and atomic that can be done by every platform.  Which means 
if you're using the services of a full-service platform like web2py the 
benchmark is already slanted against you.  It will compare the platforms 
assuming you are not using DAL, templating, routing, and all of the other 
feature that make web2py useful.  Basically they just make every app look 
like "hello world" for web servers.

The only way to compare a platform is to use a workload like the one you 
will deploy.  Mine is VERY HEAVY on database usage so the SQL database 
dominates the page load time in most cases.  I also use some heavy 
Javascript libraries (like Datatables.net) which affects load times.  The 
speed problems are never where you think they'll be.  And clever caching 
and other techniques can fix just about anything.

-- Joe


On Sunday, June 25, 2017 at 12:10:56 PM UTC-7, Ron Chatterjee wrote:
>
> Ok. I buy that.
>
> Speed is always a plus. 
>
>  Whats are the calls to run web2py with pypy? Can you share a link or an 
> example? I cant seem to find that in the book.
>
>

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to