Re: [web2py] Re: web2py added on PyPy compatibility page

2011-07-11 Thread Richard Vézina
;-) Richard On Thu, Jul 7, 2011 at 5:31 PM, cjrh caleb.hatti...@gmail.com wrote: That is a complicated question: 1) Single page load: no. This is generally an IO-bound kind of system, e.g. an infinitely fast processor would have almost no effect on response time. 2) Concurrency/Scaling:

Re: [web2py] Re: web2py added on PyPy compatibility page

2011-07-07 Thread danto
2011/7/7 cjrh caleb.hatti...@gmail.com On Jul 7, 1:27 pm, cjrh caleb.hatti...@gmail.com wrote: On further examination, it looks like leaking file descriptors is enough to mark a library as incompatible (this happened with mercurial), so I have changed web2py's to incompatible until we

Re: [web2py] Re: web2py added on PyPy compatibility page

2011-07-07 Thread Richard Vézina
Does it speed up web2py? Richard On Thu, Jul 7, 2011 at 11:28 AM, danto web2py.n...@gmail.com wrote: 2011/7/7 cjrh caleb.hatti...@gmail.com On Jul 7, 1:27 pm, cjrh caleb.hatti...@gmail.com wrote: On further examination, it looks like leaking file descriptors is enough to mark a library

Re: [web2py] Re: web2py added on PyPy compatibility page

2011-07-07 Thread cjrh
That is a complicated question: 1) Single page load: no. This is generally an IO-bound kind of system, e.g. an infinitely fast processor would have almost no effect on response time. 2) Concurrency/Scaling: generally, no. This is dominated by the DB backend, and (generally) the speed at