<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 18591 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 185, Issue 33<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Optimizing Starman startup (Victor Grousset/tuxayo)<br> 2. Re: Optimizing Starman startup (dcook@prosentient.com.au)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Wed, 28 Apr 2021 19:51:19 +0200<br>From: Victor Grousset/tuxayo <victor@tuxayo.net><br>To: 'Koha Devel' <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Optimizing Starman startup<br>Message-ID: <3f490c78-b281-b4ab-d35c-f59f20101e0a@tuxayo.net><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>Hi :)<br><br>On 21-04-28 06:40, dcook@prosentient.com.au wrote:<br>> But now that I think about it again... Jan's change is actually all we need.<br><br>That's a good news :D<br><br>So what are the perf results of this?<br><br>IIUC for your use case (spawning 120 workers with a 10 core CPU)<br>* 2 minutes 45 seconds before bug 24700, i.e. < 20.05<br>* 1 minute 30 seconds Koha >= 20.05<br>* 20 sec when validation could be disabled with a future version of <br>Mojolicious::Plugin::OpenAPI<br><br>-- <br>Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Message: 2<br>Date: Thu, 29 Apr 2021 10:00:36 +1000<br>From: <dcook@prosentient.com.au><br>To: "'Victor Grousset/tuxayo'" <victor@tuxayo.net>, "'Koha Devel'"<br> <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Optimizing Starman startup<br>Message-ID: <04cb01d73c8a$aea39af0$0bead0d0$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>There's a number of things that are improved. I should say this testing was done with a custom Koha 19.11.<br><br>First is speed, so 20 seconds to (re)start 120 workers with 20 CPUs without validation instead of taking 2 min 45 seconds w/o 24700 patch and 1 min 30 seconds w/ 24700 patch with 10 CPUs. (I was messing around with CPU count, so I don't have perfect 1-to-1 tests for everything.)<br><br>That's a start to finish of the first instance (re)started and the last Starman process having loaded app.pl and started listening for connections. The actual (re)start time for each individual process would be less. <br><br>Second is server load. With or without 24700 patch, the server load is massive (re)starting 120 workers with 10 or 20 CPUs. The server spends a lot of CPU time allocating memory during the validation process, so the server gets CPU bound during the validation process, and your instances experience latency at best and downtime at worst. <br><br>Without the validation, I couldn't detect any latency or downtime when doing a (re)start. My testing could've been flawed, but the startup time was fast enough that I didn't notice a blip. Well, the one exception is when doing a time-consuming task like a big search. If I was in the middle of a long search, obviously a restart cut that off as it severed the TCP connection. But that's unavoidable. <br><br>Anyway, I hope that helps?<br><br>As I mentioned before, we probably won't be able to skip the validation for years, unless we roll our own Mojolicious::Plugin::OpenAPI...<br><br>David Cook<br>Software Engineer<br>Prosentient Systems<br>Suite 7.03<br>6a Glen St<br>Milsons Point NSW 2061<br>Australia<br><br>Office: 02 9212 0899<br>Online: 02 8005 0595<br><br>-----Original Message-----<br>From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Victor Grousset/tuxayo<br>Sent: Thursday, 29 April 2021 3:51 AM<br>To: 'Koha Devel' <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Optimizing Starman startup<br><br>Hi :)<br><br>On 21-04-28 06:40, dcook@prosentient.com.au wrote:<br>> But now that I think about it again... Jan's change is actually all we need.<br><br>That's a good news :D<br><br>So what are the perf results of this?<br><br>IIUC for your use case (spawning 120 workers with a 10 core CPU)<br>* 2 minutes 45 seconds before bug 24700, i.e. < 20.05<br>* 1 minute 30 seconds Koha >= 20.05<br>* 20 sec when validation could be disabled with a future version of Mojolicious::Plugin::OpenAPI<br><br>--<br>Victor Grousset/tuxayo<br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/<br><br><br><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 185, Issue 33<br>*******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>