;-)
Richard
On Thu, Jul 7, 2011 at 5:31 PM, cjrh 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: generally, no. T
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 which
Does it speed up web2py?
Richard
On Thu, Jul 7, 2011 at 11:28 AM, danto wrote:
> 2011/7/7 cjrh
>
>> On Jul 7, 1:27 pm, cjrh wrote:
>> > On further examination, it looks like leaking file descriptors is enough
>> to
>> > mark a library as "incompatible" (this happened with mercurial), so I
>>
2011/7/7 cjrh
> On Jul 7, 1:27 pm, cjrh 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 can fix all the leaks.
>
> I should al
4 matches
Mail list logo
