Waitress? But it's not a single file.

On Friday, September 28, 2012 5:38:10 AM UTC-7, Massimo Di Pierro wrote:
>
> Anyway, to my knowledge cherrypy is the only pure-python single-file 
> ssl-enabled web server, apart for rocket. Are there others?
>
> On Friday, 28 September 2012 07:37:28 UTC-5, Massimo Di Pierro wrote:
>>
>> +1
>>
>> On Friday, 28 September 2012 04:57:59 UTC-5, Michele Comitini wrote:
>>>
>>> If we have to change, could we come up with a list of good candidates, 
>>> including cherrypy, and have a voting session?
>>>
>>> mic
>>>
>>>
>>>
>>> 2012/9/27 Massimo Di Pierro <massimo....@gmail.com>
>>>
>>>> Tim, creator or Rocket has not been very responsive recently. Should we 
>>>> revert to cherrypy wsgiserver?
>>>>
>>>>
>>>> On Wednesday, 26 September 2012 18:18:28 UTC-5, Michele Comitini wrote:
>>>>
>>>>> I confirm that is a rocket issue.  After a while it starts leaving 
>>>>> CLOSE WAIT sockets around until consuming all available file handles.
>>>>>
>>>>> mic
>>>>>
>>>>> 2012/9/27 Niphlod <nip...@gmail.com>
>>>>>
>>>>>
>>>>>> On Thursday, September 27, 2012 12:20:03 AM UTC+2, Massimo Di Pierro 
>>>>>> wrote:
>>>>>>>
>>>>>>> Are you telling us that under heavy load, trying to generate a new 
>>>>>>> session_id at every request using the os entropy generator 
>>>>>>> (/dev/urandom), 
>>>>>>> results in too many files open, causes tickets, and this produces the 
>>>>>>> apparent slow down? 
>>>>>>>
>>>>>>> What do you suggest?
>>>>>>>
>>>>>>>  
>>>>>> this is not the case within uwsgi....no errors show up. For 
>>>>>> production sites handling a lot concurrent requests rocket is not 
>>>>>> recommended.
>>>>>>
>>>>>> Commenting out the part generating request.uuid on main.py was part 
>>>>>> of "the hack" for case 5). Just commenting that turned out in a ~50 
>>>>>> reqs/sec more capability. The big "speed bump" (~400 reqs/sec more) is 
>>>>>> removing all the session logic.
>>>>>>  
>>>>>>
>>>>>> -- 
>>>>>>  
>>>>>>  
>>>>>>  
>>>>>>
>>>>>
>>>>>  -- 
>>>>  
>>>>  
>>>>  
>>>>
>>>
>>>

-- 



Reply via email to