> Hm. Actually, further testing seems to suggest that the order is > deterministic, and that they are applied in the order they appear in the > vassal config file, which complies with the principle of least > surprise. Please ignore us. > > For anyone else wishing to apply memory cgroup limits, you'll want to do > them in this order: > > cgroup-opt = memory.limit_in_bytes=1800M > cgroup-opt = memory.memsw.limit_in_bytes=1800M > > but turns out we actually want per-worker limits rather than per-app, > separate question on that to follow. > > rgds, > Harry + the PythonAnywhere team. >
Hi Harry, sorry for the late, yes i confirm you that cgroup writes are applied in the order they appear -- Roberto De Ioris http://unbit.com _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
