Thanks for kind help. it works, however, much slower, than memcached. :( If it could be possible and this wish list could be viewed by developers community - it's great: 1) I've tried to store raw python objects in cache and failed. Thus - I can use pickled objects either python strings in cache. It can improve performance if there will be possibility to store raw python objects too if possible. 2) when dealing with nginx enhanced memcached module ( https://github.com/bpaquet/ngx_http_enhanced_memcached_module ) nginx honors headers, stored in cache and generates 304 (not modified) response if Etag / Expires headers show that content is not out of date. This architecture pattern relly increase performance and saves traffic.
Thanks a lot again -- Regards, Lev Lemkov ________________________________________ From: [email protected] [[email protected]] on behalf of Roberto De Ioris [[email protected]] Sent: Tuesday, July 10, 2012 9:43 AM To: uWSGI developers and users list Subject: Re: [uWSGI] access uwsgi cache via nginx > But even when using pickling: when I try to access cache within django > backend - all is ok. But when I try to get data through nginx directly - > uwsgi just closes connection and nothing else happens. > > Maybe, nginx or uwsgi config I've provided is not correct? Hi Lev, nginx expect a raw HTTP output from your caching system, if uWSGI contains pickled data, nginx will not be able to use them. If you plan to only store raw http output in your cache, simply modify the cache module to write raw strings instead of pickled data -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
