[Koha-bugs] [Bug 16579] Use separate memached namespace for caching koha-conf.xml

2016-06-13 Thread bugzilla-daemon
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16579 --- Comment #7 from Jacek Ablewicz --- (In reply to Jonathan Druart from comment #3) > Why is it hard to set the env var? Maybe it's not that hard, but it needs to be done in many places, and somehow it gets

[Koha-bugs] [Bug 16579] Use separate memached namespace for caching koha-conf.xml

2016-06-13 Thread bugzilla-daemon
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16579 --- Comment #6 from Jacek Ablewicz --- Either way, I have a feeling that implementing it (fetching memcache settings from Koha config) is not going to be easy. Fastmmap caching system is still broken, because

[Koha-bugs] [Bug 16579] Use separate memached namespace for caching koha-conf.xml

2016-06-13 Thread bugzilla-daemon
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16579 --- Comment #5 from Jacek Ablewicz --- 140 miliseconds? Quite a lot - I know config file is currently parsed 3 times by an average script (for no apparent reason), but on my test setup, C4::Context->new() call

[Koha-bugs] [Bug 16579] Use separate memached namespace for caching koha-conf.xml

2016-06-13 Thread bugzilla-daemon
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16579 Jacek Ablewicz changed: What|Removed |Added See Also|

[Koha-bugs] [Bug 16579] Use separate memached namespace for caching koha-conf.xml

2016-06-12 Thread bugzilla-daemon
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16579 --- Comment #4 from Jonathan Druart --- But b is not ideal neither. You expect that memcached won't be use if the env var is not defined. We can imagine a sysop wanting to disable the cache

[Koha-bugs] [Bug 16579] Use separate memached namespace for caching koha-conf.xml

2016-06-12 Thread bugzilla-daemon
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16579 --- Comment #3 from Jonathan Druart --- I am not in favor of adding 0.15s when we are fighting to gain ms everywhere in the code, so I'd vote for b. (In reply to Kyle M Hall from comment

[Koha-bugs] [Bug 16579] Use separate memached namespace for caching koha-conf.xml

2016-06-07 Thread bugzilla-daemon
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16579 --- Comment #2 from Kyle M Hall --- (In reply to Jesse Weaver from comment #1) > I'd like to suggest that we either: > > a) drop the caching for the koha-conf.xml entirely (in my testing, this > adds

[Koha-bugs] [Bug 16579] Use separate memached namespace for caching koha-conf.xml

2016-05-25 Thread bugzilla-daemon
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16579 Tomás Cohen Arazi changed: What|Removed |Added CC|

[Koha-bugs] [Bug 16579] Use separate memached namespace for caching koha-conf.xml

2016-05-25 Thread bugzilla-daemon
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16579 Jesse Weaver changed: What|Removed |Added CC|

[Koha-bugs] [Bug 16579] Use separate memached namespace for caching koha-conf.xml

2016-05-25 Thread bugzilla-daemon
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16579 Jesse Weaver changed: What|Removed |Added CC|