https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31074 --- Comment #32 from Victor Grousset/tuxayo <victor@tuxayo.net> --- (In reply to David Cook from comment #29)
We'd need to "preload" the base code, which we don't currently do in Koha, in order to get that benefit of compiling once and then forking many times for a cheaper cost.
Thanks for all the info :)
What bad stuff could happen if an end user (managing plugins) can trigger a worker reload?
It would make for a very very easy denial of service, but it's true that someone can still do a DOS by just sending a high volume of high impact requests anyway.
Or by sending a high impact sabotaging plugin ^^" So it doesn't seem like an additional concern.
This is another case where multi-tenancy would be a problem. If one end user could trigger a worker reload on a multi-tenanted server, it would cut out for everyone. At least in this case it's isolated to their own Koha instance.
In that case of multi-tenancy with shared workers, allowing plugin management via UI would be a no anyway, right? "it would cut out for everyone" => just a few seconds of wait while the system restarts many workers but other than that it's said to be graceful so no aborted request processing IIUC -- You are receiving this mail because: You are watching all bug changes.