https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16814 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomascohen@gmail.com --- Comment #1 from Tomás Cohen Arazi <tomascohen@gmail.com> --- The indexer timeout wouldn't have any impact (the CPU footprint is small for indexer daemons), problem is memory. I'd say such a highly demanded server is a special situation that the sysadmin should be able to handle. But I'd say you will be trading memory for high CPU usage if you stick to the usual cronjobs on that many instances. For me this is a WORKSFORME -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16814 --- Comment #3 from Tomás Cohen Arazi <tomascohen@gmail.com> --- (In reply to Mirko Tietgen from comment #2)

I have ~25 test instances on a small server with 4 GB ram. I upgraded to 16.05.01, so far I can't see anything like that. 3 CPU cores at almost 0, about 2.4 GB RAM used, no swap.

What I mean, is that someone maintaining a 10+ instances server should be able to make de decision to change the enabled-by-default indexer if it was a problem on its deployment infrastructure. But the feature should definitely remain enabled by default for the average user. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16814 Mirko Tietgen <mirko@abunchofthings.net> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=16190 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16814 --- Comment #6 from Magnus Enger <magnus@libriotech.no> --- (In reply to Mirko Tietgen from comment #5)

Magnus: do you have a custom cronjob for koha-rebuild-zebra that may be running while you also use the inder daemon? I just found that here and if I had bigger data sets, that would probably make the server sad.

Not custom, but the standard cronjob set up by the packages in /etc/cron.d/koha-common was enabled: */5 * * * * root test -x /usr/sbin/koha-rebuild-zebra && koha-rebuild-zebra -q $(koha-list --enabled) I just tried commenting out this, setting USE_INDEXER_DAEMON="yes" and rebooting, and load, memory usage and swap went through the roof pretty instantly after the reboot. I am fine with WORKSFORME - as I said, a server with this many instances is probably an edge case. But, should we at least remove or comment out this: */5 * * * * root test -x /usr/sbin/koha-rebuild-zebra && koha-rebuild-zebra -q $(koha-list --enabled) from /etc/cron.d/koha-common (debian/koha-common.cron.d in git) now that the daemon is activated as default? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16814 --- Comment #8 from Magnus Enger <magnus@libriotech.no> --- I can do separate bug and patch for that. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16814 Magnus Enger <magnus@libriotech.no> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=16823 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16814 Magnus Enger <magnus@libriotech.no> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #11 from Magnus Enger <magnus@libriotech.no> --- I upgraded my production server last night. It is a beefier server with "just" 35 instances. No sign of anything getting stressed out. I'll conclude that the problem with the test server was too many instances, not enough resources and mark this as WORKSFORME. Bug 16823 remains open, though. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.