Il giorno 12/feb/2012, alle ore 21:23, Łukasz Mierzwa ha scritto: > Dnia niedziela, 12 lutego 2012 17:57:14 Roberto De Ioris pisze: >> As promised, the zerg-mode has been greatly improved. >> >> The zerg-mode has been (unexpectedly) preferred as a way to reach >> really-gracefully reloads and to make real-time tests, instead of using it >> to better manage scaling. >> >> For that reason, i have added a new options to avoid taking down >> instances if a zerg server is not available (--zerg-fallback), and a new >> server/gateway family, named zergpools. (they are highly configurable >> zerg-server-only processes) >> >> The doc has been updated too >> >> http://projects.unbit.it/uwsgi/wiki/ZergMode > > If I get it right zerg mode allows to add/remove instances from any app (if > enabled). Does it gives any advantages over cheaper mode other then the fact > that one can add unlimited number of new workers, where with cheaper one is > limited to max value defined at app start? Plus one needs to start/stop > instances manually with zerg mode. Do I get it right?
yes, you get it right. > Can we think of cheaper as a internal and very simple way of scaling for > applications, and zerg mode as a externally controlled way, so that one can > plug it into some system that adjusts workers count? yes, look at the broodlord mode for an example of externally managed scaling. > I just wonder why and when someone would use one or another. > i think that currently the cheaper mode is more appreciated even if it can look "old-fashioned" being based on the old-paradigm of spare processes. Broodlord mode (as an example) is based on socket listen queue, so it is a better metric of overloads. Maybe in the feature we can combine the code. By the way, for now zerg mode has win as a fast-test/fast-reload platform, so i will continue working on that side :) -- Roberto De Ioris http://unbit.it JID: [email protected] _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
