Is the talk recorded somewhere? On Aug 1, 2013 12:32 AM, "Roberto De Ioris" <[email protected]> wrote:
> > > > Hi Roberto, > > > > > > > > Great talk! Unfortunatly I couldn't attend. > > > > > > > > We're building something similar to what you've demo'ed, it will not be > as realtime as the game, but requires realtime responses within a ~200ms > timeframe. > > > > For the web part (the standard request/response cycle) we're using > Django. For the realtime notifications and updates we'll be using > websockets that connect to a dedicated daemon process which runs on > gevent. > > > > > > > > In your talk you mentioned something about uwsgi channels as an > > alternative > > to zeromq or redis pub/sub for IPC, but mentioned for your case it would > be > > too expensive to set up. In our case we'd need each Django worker to be > able > > to push info to the daemon, would uwsgi's channels be a good fit in this > case? What would be the main advantage using these channels compared to > say > > zeromq? > > Hi, uWSGI channels have been removed during 1.5/1.9 development cycle, > there is a new draft by Lorenzo Masini > (https://github.com/unbit/uwsgi/issues/338) that should address all of the > flaw of the previous attempt. > > 200 ms are really "far" from realtime, so zeromq will be a perfect fit for > your purpose and you will be able to easily exchange messages between > django and the websockets app. > > > > Another thing is we need to share permissions among the workers and the > daemon process. Querying these each time from each independend process > would > > be too costly ofcourse, so caching seems like the way to go. I've read > that > > uwsgi's caching mechanism is quite fast, even faster than redis, do you > know > > exactly how it compares? > > it is faster than redis when no ipc is involved (read: when you do not use > it over the network). The cache2 allows bitmap mode so you do not need to > have fixed size for items. > > Take in account you can spawn a uWSGI instance with a pool of workers > dedicated to django and another pool to websockets+gevent, in such a way > you can have shared caching for free. It is a pretty complex setup but i > use it successfully in various project. > > > -- > 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
