Hello Roberto,
seems there are no easy way to yield from the view function, as I can't yield
HTML response with standard django functions (yield
render_to_response('index.html')) as django doesn't wait for
the generator from the view function and raises error. so seems
then django unusalbe in async mode?
looking into bottle, but still interested to make it in django.
so seems not
Monday, May 16, 2011, 10:09:12 AM, you wrote:
> Il giorno 16/mag/2011, alle ore 11.05, [email protected] ha scritto:
>> Hello Roberto,
>>
>> I just thought about templates layer, but seems with simple templates
>> didn't find big difference - about 10% (async 10% slower).
>>
>> also do you have any idea, why I have these error messages in async
>> mode?
>>
>> accept(): Resource temporarily unavailable [utils.c line 525]
>> accept(): Resource temporarily unavailable [utils.c line 525]
>> accept(): Resource temporarily unavailable [utils.c line 525]
>> accept(): Resource temporarily unavailable [utils.c line 525]
>> accept(): Resource temporarily unavailable [utils.c line 525]
>> accept(): Resource temporarily unavailable [utils.c line 525]
>>
>> and more strange, that due to apache bench stats I don't have any 500
>> Errors, so all responses have HTTP code 200.
>>
>>
> Which uWSGI version ?
> Seems an unneded "thundering herd" problem report. (multiple
> processes running for accept() the same request)
> --
> Roberto De Ioris
> http://unbit.it
> _______________________________________________
> uWSGI mailing list
> [email protected]
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
--
Best regards,
Test157 mailto:[email protected]
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi