On Aug 31, 2009, at 1:32 PM, Alex Clemesha wrote:

> On Mon, Aug 31, 2009 at 8:59 AM, William Stein<wst...@gmail.com>  
> wrote:
>>
>>
>> On Mon, Aug 31, 2009 at 8:45 AM, Thierry Dumont <tdum...@math.univ- 
>> lyon1.fr>
>> wrote:
>>>
>>> William Stein a écrit :
>>>>
>>>>   The first thing I plan to do is consider switching from
>>>> twisted to Django, as is done in codenode -- see http:// 
>>>> codenode.org/ --
>>>> hopefully, even sharing code with that project.
>>>
>>> Django is used (generally) with mod_python under Apache. Does it  
>>> means
>>> that the whole Sage will be served by Apache and mod_python? This  
>>> would
>>> (may be) improve performances, no ?
>>>
>>
>> I doubt it would impact performance in practice.  Improving  
>> performance is
>> going to require improvement to the rest of the server code.
>>
>> For Sage, the default would be that the notebook is still served  
>> by some
>> Python library -- most likely Twisted of course -- but that at  
>> least the
>> option of replacing use of Twisted by Apache would exist.
>>
>> Codenode guys -- since I speak from 0 experience (!) -- any  
>> comments on the
>> relative performance of Apache versus Twisted?
>
> For what we are trying to do, i.e. write an "online programming
> notebook" (Sage notebook / Codenode),
> the bottleneck is definitely going to be the processes that are
> actually executing
> the code, the communications from these processes back to the  
> "Frontend",
> and the additional data operations like saving user state.
>
> Consider a "very small" load on a regular website, maybe 100 users  
> at once doing
> various things like reading static articles or checking out photos. In
> the case of
> the Sage Notebook or Codenode, that's *100 python/sage processes* -
> Apache vs Twisted doesn't make much of a difference here.

Though we're all just pulling numbers out of the air until we have  
actual benchmark data, I agree with you that performance probably  
isn't a big issue here. I see the advantages o Apache being that  
authentication, ssl, etc. are abstracted away and often already  
integrated into the existing environment which is one less thing to  
worry about.

That being said, I'm a strong proponent of the benefits of WSGI.

- Robert


--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to