<!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 18647 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 186, Issue 2<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: Why is config ($KOHA_CONF) stored in memcached ?<br> (Tomas Cohen Arazi)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Sat, 1 May 2021 09:53:14 -0300<br>From: Tomas Cohen Arazi <tomascohen@gmail.com><br>To: Julian Maurice <julian.maurice@biblibre.com><br>Cc: koha-devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Why is config ($KOHA_CONF) stored in<br> memcached ?<br>Message-ID:<br> <CABZfb=VOKf+VuFzdcb2vydmTNWi8aJfV2tdEpAAD5jDyNt4_Gg@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>I vote for fixing it so the file is only hit the first time.<br><br>El vie, 30 abr 2021 a las 14:19, Julian Maurice (<<br>julian.maurice@biblibre.com>) escribió:<br><br>> Hi all,<br>><br>> Maybe it's a dumb question, but I don't understand why the config is<br>> stored in memcached as:<br>> - memcached server address is in this config, so we need to read<br>> $KOHA_CONF file first in order to connect to memcached server<br>> - config is kept in memory forever ($C4::Context::context), so we<br>> shouldn't need the cache once starman has started.<br>><br>> If you add a warning in Koha::Config::read_from_file, you'll see that<br>> the file is read 3 times per worker, even when the config already exist<br>> in cache (it's read 4 times when the cache is empty).<br>> It's read each time we call Koha::Cache->new (+ in C4::Context->new if<br>> the cache is empty)<br>><br>> Shouldn't we read the file only in C4::Context->new (without using<br>> cache), and make Koha::Cache use C4::Context->config instead ?<br>><br>> --<br>> Julian Maurice<br>> BibLibre<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>Tomás Cohen Arazi<br>Theke Solutions (http://theke.io)<br>✆ +54 9351 3513384<br>GPG: B2F3C15F<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20210501/718eb120/attachment-0001.htm><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 186, Issue 2<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>