[Koha-bugs] [Bug 31074] Cached plugin code is used in Koha even after changes to plugin (install/upgrade/uninstall)

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31074

--- Comment #34 from Victor Grousset/tuxayo <victor at tuxayo.net> ---
(In reply to David Cook from comment #33)
> Everything would be configuration driven, so you could still have people
> upload plugins, and Koha could put them in the right place.

If the workers are shared, then all plugins also, right? So before triggering a
too wide reload the issue would be simply letting tenants installing plugins
because that would affect the other.

---

> Yes, it should be graceful, so no aborted request processing, but the length
> of the wait is variable. 
> 
> For instance, if you have 8 CPUs and 400 workers, and each worker needs 100%
> CPU for a few seconds at startup then you're going to have a long wait
> before the full system is operational.

The ratio between threads and workers should never be like this, right? Because
the point of workers is to have parallel request processing when having
multiple threads. So 8 CPUs could never process 400 queries at the same time.
(even if a lot of time is DB wait) So the practical number of workers would be
much lower. And that also caps the reload time. Like a few seconds a most?
Beyond means not having enough threads to be able to use that much workers
anyway.

All this is to be sure whether or not the possibility of triggering a reload is
viable or not. (option 2 of comment 19)


---


> (Some day when I have more time I'm going to look again at reducing CPU consumption
> at startup time for the Starman workers...)

Just in case that might help, you mentioned preloading earlier, is that
--preload-app ?
https://metacpan.org/dist/Starman/view/script/starman#-preload-app

-- 
You are receiving this mail because:
You are watching all bug changes.