-------- Guillaume Quintard writes:
> There's a thing that has been bugging me for years, and maybe it's time to > change/break it with 8.0. > > The fact that thread_pool_min/max is per pool is generally pretty confusing > to users. Could we consider retiring them and have simpler thread_min/max > parameters that would be split evenly across pools? > > It's a bit more code, but it would save me a few discussions when > teaching/supporting new users :-) We talked about this at bugwash today: No objection (but Nils on vacation) Probably keep old params around undocumented, and just multiply by #pools and set the new param. Also: Was changing #pools on the fly ever useful for anybody or should we GC tha feature and simplify the code ? Care to open a ticket, preferably with a patch ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [email protected] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
