https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36721
--- Comment #2 from David Cook <[email protected]> --- While this doesn't have to do with preloading per se, I am seeing a slowdown: I'm noticing on startup that each Starman worker spending some time doing some web requests... which are probably related to JSON::Validator. IP addresses: - 104.26.3.209 - 104.26.2.209 - 172.67.71.88 These are the IPv4 addresses for json-schema.org. I notice the first web request gets redirected as well: write(21, "GET /draft-04/schema HTTP/1.1\r\nUser-Agent: Mojolicious (Perl)\r\nAccept-Encoding: gzip\r\nHost: json-schema.org\r\n\r\n", 111) = 111 read(21, "HTTP/1.1 301 Moved Permanently\r\nDate: Tue, 30 Apr 2024 02:27:33 GMT\r\nContent-Type: text/html\r\nTransfer-Encoding: chunked\r\nConnection: keep-alive\r\nCache-Control: max-age=3600\r\nExpires: Tue, 30 Apr 2024 03:27:33 GMT\r \nLocation: https://json-schema.org/draft-04/schema\r\nReport-To: {\"endpoints\":[{\"url\":\"h"..., 131072) = 870 -- Back in July 2020, there was a problem with swagger.io, which caused Koha to fail to startup. So in bug 23653 we started using a local copy of the schema. But in Bug 30194 it looks like that undid bug 23653... but that was for swagger.io. Note if json-schema.org is down (just map json-schema.org to localhost to reproduce), Koha appears to start, but the API doesn't work. You'll get 404 errors for every API endpoint. -- It looks like we can provide our own string to the $schema->specification(), so we can restore the idea behind bug 23653. That should insulate us from issues with json-schema.org and make for faster startup times. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
