> Should I run simple wsgi application on the > same > instance as subscription server, import uwsgi module in it and lookup > those > informations there? It would be good solution for me but looking at the > list > of exposed statistics I not sure if those informations are there. > BTW is subscription server single process? Can I have multiple SS > processes > listening on single port?
Hi Lukasz, the subscriptions statistics are currently discussed on irc, mainly with Yann Malet of Lincoln Loop. It is a very useful part for sure, but very hard to implement as uWSGI shared-dictionary are hard to scan without blocking (it will impact performance) You can spawn an unlimited number of fastrouter simply adding multiple --fastrouter <socket> uwsgi --fastrouter :3031 --fastrouter :3032 --fastrouter :3033 is perfectly valid and will ends with 3 fastrouter You can share sockets too using --shared-socket feature uwsgi --shared-socket :3031 --fastrouter =0 --fastrouter =0 --fastrouter =0 means: spawn 3 fastrouter bound on first shared socket as well: uwsgi --shared-socket :3031 --shared-socket :3032 --fastrouter =0 --fastrouter =0 --fastrouter =1 will bind two fastrouter on socket :3031 and one on :3032 you can even make a total mess: uwsgi --shared-socket :3031 --shared-socket :3032 --fastrouter =0 --fastrouter =0 --fastrouter =1 --socket =1 --module yourapp ...and you will end with fastrouters and your apps all bound to the same addresses :) > P.S. I'm just discovering uWSGI and so far it seems amazing project, how > could > I not hear about it before? Take in account that only recently it got an almost-good documentation (even if not up-to-date), before that, it was a extreme-tech-only project :P -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
